Deployment notes

[endashaw.adane]

I have two envts, Dev and Testing. Every time a code is committed, release created and deployed to Dev. I’ve used a release note template and release notes are displayed properly for each. At the end of the day, the last release will be deployed to Testing. I used #{Octopus.Deployment.ChangesMarkdown | MarkdownToHtml} in email notification. I was expecting this will bring all release notes since last deployment. However, it is not. It always shows the last release note both in email as well as preview. I’ve also used the following, but still shows the last release notes. I am using Octopus Server 2019.13.7
Deployment contained releases:

#{each change in Octopus.Deployment.Changes}

#{change.Version}

#{change.ReleaseNotes | MarkdownToHtml}

#{/each}

[paul.calvert]

Hi @endashaw.adane,

Thanks for getting in touch!

To help figure out where this is failing, would you be able to provide some additional information for me?

Firstly, can you provide the full release version number of one of the releases that this is affecting? Does it include any pre-release tags? e.g. 1.0.1-beta

Second, if you view the deployments for the test environment within the UI, do you see full deployment notes on the right hand side? Or does it match what is appearing in the email?
e.g.

Regards,
Paul

[endashaw.adane]

@paul.calvert,

Thanks for your quick reply!
I’ve used pre-release tag as ‘bau’ I dont have different version number from one envt to another. I am alwasy promoting the last release to the higher envt. The UI also shows the same as it is in the email.

[endashaw.adane]

@paul.calvert,

e.g. The following releases are deployed in Dev. The latest is 10.26-5-bau-1bc894b. The UI and the email shows release notes only for 10.26-5-bau-1bc894b.
10.26-4-bau-75b3c6a
10.26-5-bau-1bc894b

[paul.calvert]

OK, I had a feeling that may be the case.
Deployment notes are handled differently for pre-release versions. Octopus will only gather up multiple release notes into a deployment note for full version releases. There is more detail on this here: https://octopus.com/docs/releases/deployment-notes#Versioning

[endashaw.adane]

I think that is the reason. I am not following that kind of versioning rules. Is there any other means to consolidate a release notes?

[paul.calvert]

The only other way would be to do this manually using a script and the API. You could retrieve a list of releases created on the current day, then extract the release notes from each one. Then, each set of notes could be added to output variables and used within your email step.
This isn’t something that I’ve done before so I don’t have any examples available for this though.

We do have a repository of example API scripts available that may help you get started if you decide to go this route: https://github.com/OctopusDeploy/OctopusDeploy-Api

Regards,
Paul