Handle a duplicate release number from TeamCity


Here is our scenario. In almost all cases, all releases originate from TeamCity, which passes in the release number (same as our teamcity build number).

However, we occasionally need to manually create a release in octopus when there are no code or build changes due to step template changes, variable changes, etc.

This increments the release number, and the next time teamcity pushes a release it fails because octopus already has a release with that number.

Is there a parameter or something we can pass to have this work more gracefully?


Hi Stephen,

Thanks for getting in touch!

Usually the best way is to version your manual release with a different pattern. for example that won’t clash with the next auto generated one.

Hope that helps!