Support YYYY, MM, DD variables in version templates

[nblumhardt]

http://help.octopusdeploy.com/discussions/questions/2276-release-versioning-parameters

E.g.

Octopus.Date.Year
Octopus.Date.MonthNumber
Octopus.Date.DayNumber

[dtjensen]

Nick - I have used other date-based versioning in the past as well like "day in year", etc. So, when you guys think about this one, you may want to think bigger than the few examples I listed in the original question.

Actually, if there is a way to allow entering a powershell scriptlet that could yield a result in the form of a variable, that may be the most flexible long term solution. Because people use lots of schemes when creating their version numbers. Just a thought...

[nblumhardt]

Thanks for the ideas - was planning to spend a bit of time thinking through other options.

Running PS at this point may not be viable, but extending the Octopus variable syntax with simple expressions is a possibility at some point. Guess we'll collect some more scenarios as we go.

[PaulStovell]

Done in 2.5:

#{Octopus.Date.Year}.#{Octopus.Date.Month}.#{Octopus.Date.Day}.#{Octopus.Date.DayOfYear}

Output:

2014.06.16.167

Month and Day are always 2 chars. Day of year is variable length.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.