Octopus variable for package's release notes
Just like there are variables such as
.package.nugetpackageID
.package.nugetpackageversion
It'll be good to have an Octopus variable that holds the value of the package's release notes metadata.
There are scenarios where it is useful to add data at build time to the package's release notes, and by having an Octopus variable olding this data, it'll be pretty ease to use that info on other Powershell steps later on the deployment.
Dalmiro Grañas
shared this idea
-
Craig Shea
commented
Wholeheartedly agree. I created a variable in my deployment project called ReleaseNotes. So, in the release notes field of a release, I put in #{ReleaseNotes}. But then, on the OD releases page, all I see is releases with a huge {RELEASENOTES} header--not exactly what I want to see--but our release notes are based off of a template.
So, in lieu of providing a Release Notes template, a variable that would be expanded by the Releases Page as well as during deployment would be great.