Publish Lower Versioned Package

Legacy Uncategorised
1

We have made a last minute decision to switch assembly versioning and our Octopus (3.4.9) release versioning for this project is set to “Use the version number from an included package”. Our original versioning was 2017.n.n.n and our new is 2016.n.n.n. Because of the lesser package version I cannot publish the packages (using OctoPack) to the built-in package repository. I cannot adjust the Repository retention because we have have more than one department sharing the same deploy server so I don’t believe deleting the physical packages will help. I’ve found several solutions for redeploying the same version but none have worked for my situation. Is there any option available for publishing lower versioned packages?

2

Hi Mark,

Thanks for getting in touch.

Unfortunately there is no option for publishing lower versions of a package. If you’re on a shared instance and are concerned about deleting your 2017 packages, perhaps you could host another (external) package repository and publish your new 2016 versions there (see the ‘Using external repositories’ section of the Package repository documentation). Otherwise, deleting your 2017 packages would be the only clean way of switching to your new 2016 assembly versioning.

Depending on how many packages you have, are you able to schedule an Octopus maintenance window so you don’t upset other departments, then download the 2017 packages, change their versioning to 2016 and re-upload?

Hope this helps.

Cheers
Mark

3

Thanks for the quick response. Can you elaborate on the second option? When I download packages it does not remove them from the library so I’m not clear on how this would allow me to re-upload with a lower version?

4

Hi Mark,

Sorry, I mis-typed that. I meant you could download the 2017 packages locally, then delete those packages from Octopus, rename the local copies to your new 2016 version-scheme, then re-upload.

But again, I don’t know how feasible that is and how many packages you’re dealing with.

Cheers
Mark

5

Downloading and deleting all, then re-uploading with a newly built lower versioned package absolutely worked. It is a bit of work up front but as long as the target result is achieved, it works for me. Thank you for your help!