When deploying a release to an environment, default the Comments from all the Release Notes since the last deployment to that envioronment.
Part Two of a 2-part idea.
When we deploy to production we generally would like to, include in the comments all the release notes from all the releases since the last deployed-release to that environment.
But it IS admittedly a bit of a chore.
If Octopus did it, then it wouldn't even be a chore at all and we would continue to love Octopus and feed it plenty of sailors!
<3 u
Jason Glover
shared this idea
We are implementing this in conjunction with some tighter integration to the work item trackers (like Jira and GitHub). Release coming soon.
5 comments
-
Reza Rahmati
commented
-
Brian Karcher
commented
This would be amazingly useful for us and exactly what we have been looking for.
-
Sam “Betty” McKoy
commented
@peter that would only work for the first environment. If you fixed a bug in that environment then the next one would only see the bugfix note.
You could have a branch per environment but that basically defeats the point of octopus.
-
Peter Dolkens
commented
I think you're trying to collate a collection of programmatically generated release notes from a build server / version control system here - is that correct?
If so, which build system are you using - I'd suggest having a "release" or "master" branch, which you only merge into when you're ready to go to production - your auto-generated notes should then contain all check-ins since the last "release"
Voted on your part 1 though
-
Jason Glover
commented
This is Part Two of a 2-part idea..... (part one ~ http://octopusdeploy.uservoice.com/forums/170787-general/suggestions/4503012-when-creating-a-new-release-default-the-releases-)