Is anyone faced with such problem as wrong number in "view xxx changes" in build? I dunno why, but it show not only commits between build, but everything else! For example I had two commits between releases, but it show me 300+ changes. My git showed below. I expect 'View changes' show me only commits between r-2.8 and r-2.9.
The following list describes which changesets are shown in the run details for different pipeline run types:
This info is based on walking through many YAML pipeline runs. Corrections/refinements to this answer would be helpful.
This is news to me as of today (and I have an audit meeting in an hour, so this will be interesting).
I think that this means that CI runs are not useful for the purpose of audit, change management, release notes, etc.
If the above info holds, then we'll have to sort out how to have useful info in pipeline run history. May be that CI is turned off and YAML conditionals take care of what can be deployed where, with PR triggers and manual runs as the possible initiators.
Update:
A deployment from today showed all changesets for the branch rather than diffs, so we need to rule that one out.
Update - 2021-09-08:
The Environments area under Pipelines seems to be accurate every time. It's a different approach and is a few clicks away from the pipeline run details screen, but it does happen automatically if you're using the YAML "deployment" type of job.
It shows all the changes/Commits since day one, not the changeset between 2 builds. I am sure there is better solutions for this, but we normally auto tag in each build with the build number, then hop over to the repo history view to see the relation between builds and commits
Also including a release note seems a good idea, as it has the associated commits:
