Our packages, which comes from Visual Studio Online build server, is named with the following pattern:
version-date-seq
giving packages like
1.0.0-v20150422-1
1.0.0-v20150422-2
…
1.0.0-v20150422-10
1.0.0-v20150422-11
Octopus will sort these four packages in the following order:
1.0.0-v20150422-2
1.0.0-v20150422-11
1.0.0-v20150422-10
1.0.0-v20150422-1
This is a problem, since it will not make new releases for the 10ht and 11th packages. It believes that the 2nd is the newest.
At least this is how I have concluded. We only get 9 releases/deployments each day…
Is this a bug in octopus, or is it an error in our naming scheme?
(we are still on octopus v2.5.8.447)