![]() What this does is it informs OctoPack about the files that you want to include in the deployment package. Create a NUSPEC file for your project, and include the folders that are not currently included in the project. So, in order for you to never have to resolve another conflict in generated files again, here's my guide on how to set up your project so they play nice with TeamCity and OctoPack. ![]() NET project, and pushing the generated DLL files to source control, and then having to resolve conflicts within the DLL files generated by the build. So, if developer A was working on a SCSS file which was referenced in the main stylesheet, and developer B was working on a separate SCSS file, also referenced in the same main stylesheet, why should either one have to resolve a conflict caused in the file generated by the task runner? This introduces an unnecessary problem - conflicts in generated code. This is a problem, because this means that all files generated by your task runners, be it Gulp or Grunt, will have to be included in the project and pushed out to source control. However, OctoPack will only pack files that are included in the CSPROJ file, and in the case of static files, have Build Action set to Content. Octopus Deploy has a nice NuGet package, called OctoPack, for generating Octopus Deploy-compatible NuGet packages out of.
0 Comments
Leave a Reply. |