I have one Project.sln in my GitRepo. And I need to build 4 NuGet packages with different configurations (local, qa, sandboxes and production). I am using TeamCity with Octopus Deploy.
In TeamCity, my build configuration has the following build steps:
1) NuGet Installer
2) Build Project.sln with *Local* Configuration
3) NuGet Pack with using .csproj file
4) NuGet Installer
5) Build Project.sln with *QA* Configuration
6) NuGet Pack with using .csproj file
7) NuGet Installer
8) Build Project.sln with *Sandbox* Configuration
9) NuGet Pack with using .csproj file
10) NuGet Installer
11) Build Project.sln with *Production* Configuration
12) NuGet Pack with using .csproj file
And I have the following problems:
1) When I use the AssemblyInfo patcher, it only makes one NuGet batch file. In step 3, TeamCity creates a package named 2.2.1.% Build.counter%. And in step 6, he creates a package with the same name and overwrites it. It does the same in steps 9 and 12. Finally, I only have one NuGet package with the latest configuration (in my case, Production).
I want to have 4 such packages:
2.2.1.%build.counter%_local
2.2.1.%build.counter%_qa
2.2.1.%build.counter%_sandbox
2.2.1.%build.counter%_production
2) Octopus. TeamCity ( 4 , AssemblyInfo), (Project), "some" ( QA) QA, Octopus NuGet. - "". , , TeamCity.