We accidentally used a "wrong" versioning scheme for our releases, so the first month or so builds/artifacts were created with 1.0.x version numbers. Now we've switched to 1.0.0.x, and I used the "trick" described by others to set the clean-up rules to 1 day or 1 build to get everything cleaned up. However, for some reason one of the four build steps that generate nuget packages has "left" two artifacts in the repository with the old numbering scheme, so when I try to create a new release in Octopus Deploy, the old release is used by default, as the version is (wrongly) newer.
Currently we've been building 184.108.40.206, previously 220.127.116.11 etc. But Octopus deploy sees the following when browsing the artifact feed
- 1.0.754 <---- appears as "newer" due to the old/wrong number format
also, the attached package feed extract shows how the old versions appear.
Browsing the Teamcity artifacts folder on disk shows only the two newer builds, not the old ones.
I can't see the old builds (1.0.754 and 1.0.708) in the build history, so the "build" itself is removed, just not the artifacts.
I can't remove the two old artifacts - no matter how I've set the project cleanup settings, it just isn't possible for me to delete them.
How do I fix this? Create a completely new project and hope that deleting the old projects will empty the artifacts list in the database?
I would be OK to completely clear the entire database for this project - alternatively I might just have to up the version to 1.1 and live with that.
Ideas are very welcome :)
Attachment(s):package feed extract.xml