![]() The trick to avoiding that in future was to have the compile/version/publish steps all in one Teamcity build (rather than sequential builds) so that you could never push the same build number twice. It took me a while to realise this was actually by design - an earlier build had already pushed that exact package and version and so I could not overwrite it. So I tried to push the package manually from the command line like below and got the same error: Teamcity will create nuget package with version 1.0.0.9, all the dlls that is in the package is the correct version, and the Release in Octopus, that was deployed has got the same version number, but the packages that octopus uses is of an earlier package eg 1.0.0.5. Octopus was returning a 400 Bad Request status to nuget.exe. However when I ran the publish step I would get an error in the Teamcity logs and the publish would fail. Create and deploy the release in Octopus.Some of the features offered by Octopus Deploy are: Deploy on-premises or to the cloud, securely. Use a teamcity nuget publish build step to push the package from the teamcity artifacts into the built in Octopus package repository Octopus Deploy can be classified as a tool in the 'Deployment as a Service' category, while TeamCity is grouped under 'Continuous Integration'.When you use TeamCity and Octopus together, the goal is to let TeamCity do what it does best build and let Octopus take care of deployments. This means the bits you tested in your test environment are the same bits you deploy to production. These releases are then pushed from environment to environment. Octopus retrieves the nuget package from the build server, packages them up into numbered releases. Like TeamCity, Octopus is free for small teams. Octopus integrates with the TeamCity builds by through TeamCity’s nuget server. Msbuild MySolution.sln /t:Build /p:RunOctoPack=true Where TeamCity is a build automation server, Octopus is a deployment automation server. Compile the solution using Teamcity and msbuild, specifying the octopack build property to output packages.Install the Octopack nuget package in each deployable project in the solution.Our build process goes a little like this: The quick answer is that you cannot push the same package and version to the built in octopus deploy package repository - if you try you get 400 (Bad Request). ![]() Stumbled on a little gotcha today when using nuget packages as deployment artifacts to be send to Octopus Deploy and thought it worth documenting so i don't forget next time.
0 Comments
Leave a Reply. |