Thanks to Richard's latest update of the Generate Release Notes based on Release Comparison task, version 2.9.6, we can avoid release notes being overwritten when we re-deploy a release stage that generates the release notes as covered in the auto generating release notes in azure devops pipelines blog post.

What's the issue?

We step through a release pipeline, which includes a stage where we auto generate the release notes, based on the linked work items and change from recent release.

For some reason, we decide to re-deploy the stage that auto generates the release notes. As there are no differences from the last release, the Generate Release Notes based on Release Comparison extension will generate empty release notes.

When we run the Git based WIKI Updater task, we overwrite the good release notes with the now empty release notes. Not cool!

How do I avoid this issue?

To skip the release notes generation when re-deploying, update the Generate Release Notes based on Release Comparison and Git based WIKI Updater tasks as follows:

Generate Release Notes based on Release Comparison

  • Under Advanced options, select No generation on re-deploy.
  • Task will succeed partially if the generation is skipped:
  • Task will also insert this warning in the log file:

Git based WIKI Updater

  • Under Control Options, select Custom conditions for Run this task.
  • Specify a custom condition, for example do not run the task if there were any partial failures.
ne(variables['Agent.JobStatus'], 'SucceededWithIssues') 

Thanks Richard, this latest feature update has made this very simple!