Do you avoid auto generated version numbers?
31/05/2016 9:21 AM by
release needs to have a version number. However, version numbers need to be
generated during the Build phase not the Release.
the following scenario: Your Build system generates a NuGet package with
version 220.127.116.11 that is pushed to Octopus Deploy NuGet feed. In Octopus Deploy
you create a release using the default configuration. When you create a new
release you will see 0.0.1 instead of 18.104.22.168. As you can imagine, it is
impossible to tell from the release what version number of the application was
really deployed. Hence you should change the versioning and use the package
Example - Version number is auto-generated by Octopus Deploy
Example - Version number is inherited from a NuGet package
Do you feel this rule needs an update?