Versioning in Octopus Deploy (Part I)

You may also like...

4 Responses

  1. Samuel Nissim says:

    As for how to version your NuGet packages, check out the GitVersionTask NuGet package. It uses SemVer to automatically version your assemblies (and thus your NuGet packages), in accordance with GitFlow.

  2. Andrew says:

    This was good, thanks for the info. Thinking we might start doing this as make sense

  1. February 27, 2015

    […] This will dynamically generate a new number for each build and change the version number for your NuGet packages as well. The great thing about this versioning technique is that it’s simple and will always increment the value over time as the build number is really a date reference and the revision is a relative time on the day of the build. This makes sorting easy and if you use the Octo.exe, you can configure it to use the latest version of your NuGet package which is perfect for continuous deployments. You can read more about versioning in my deep dive post on Versioning in Octopus Deploy (Part I). […]

  2. August 13, 2015

    […] the deployment will use the latest version of the NuGet packages. Keep this in mind. This is why versioning is important – especially in Octopus […]

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.