Force deploy fails with version number

Legacy Uncategorised
1

http://help.octopusdeploy.com/discussions/questions/154-force-re-deployment-of-existing-packages-checkbox

Regarding this previous post, I’ve got a similar problem.

I also want to force reployment of existing packages, but I don’t want to increment the version number. The version number is tied to a change in my source control, I simply want to redeploy the build using the same version number. Even with force enabled this fails when I try it. Is there any way around this?

Will I have to rely on my CI for build numbers? I kind of liked the way I could tie my source control, CI (team city btw) and octopus together with the same number.

2

Hi Rich,

Can you attach a copy of the deployment log when you do a deployment with “force package redeployment” checked?

Paul

3

Paul

I’ve changed this requirement and got it to use the CI build number now.

Thanks

Richard