Release note generator: No Commits or Workitems in Release pipeline

[JeroenvdBurg]

First of all thanks a lot @rfennel for you work on all the azure devops extensions.

We have our github repo linked to azure devops. We link our commits with AB#123

When using The Releasenotes generator in the YAML build pipeline it detects the linked workitems and commits.

When creating a release with the (classic) release pipeline it is getting the correct builds to diff but does not indicate any changes in commits or workitems.

Any ideas what could be wrong?

2021-11-14T10:27:12.6350946Z Looking for the [_dotnet6preview_app] in the most recent successful release [Release-19]
2021-11-14T10:27:12.6353367Z Found artifact [_dotnet6preview_app] with build number [20211114.10] in release [Release-19]
2021-11-14T10:27:12.6353839Z Checking what commits and workitems have changed from [20211114.10][ID 84] => [20211114.11] [ID 85]
2021-11-14T10:27:12.6354402Z Defaulting on the workaround for build API limitation (see issue #349 set 'ReleaseNotes.Fix349=false' to disable)
2021-11-14T10:27:12.6354979Z Using workaround for build API limitation (see issue #349)
2021-11-14T10:27:12.8651413Z Getting test associated with the latest build [85]
2021-11-14T10:27:13.2047131Z Adding the build [85] and its associations to the unified results object
2021-11-14T10:27:13.2048752Z Detected 0 commits/changesets between the current build and the last successful one
2021-11-14T10:27:13.2049704Z Detected 0 workitems between the current build and the last successful one
2021-11-14T10:27:13.2050531Z Found 0 tests associated with the build [85] adding any not already in the global test list to the list
2021-11-14T10:27:13.2829482Z Found 0 manual tests associated with the build [85] adding any not already in the global test list to the list
2021-11-14T10:27:13.2853747Z
2021-11-14T10:27:13.3546198Z Removing duplicate Commits from master list
2021-11-14T10:27:13.3546621Z Expanding the truncated commit messages...
2021-11-14T10:27:13.3546958Z Expanded truncated commit messages 0
2021-11-14T10:27:13.3547244Z Leaving CS in default order as returned by API
2021-11-14T10:27:13.3551830Z Find any WorkItems linked from GitHub using the AB#123 format
2021-11-14T10:27:13.3552594Z Adding 0 found using AB#123 links in GitHub comments

The dialog in Azure Devops shows the related commits and workitems

[rfennell]

The is no real support for getting the AB#123 associated Work items via the API. Hence, I find the AB#123 links by string matching against the associated commit messages. Looking at the log, as you find no associated CS it can't do the lookup.

Remember the release notes are based changes since the last run, so when using Classic Releases, if none of the build artifacts have changed there will be no associations, chance no lookup

[JeroenvdBurg]

thanks a lot for your reply. There is one commit changes between the two artificats: 20211114.10][ID 84] => [20211114.11] [ID 85]
I don't know why it does not find any CS. i believe that the experience is better with linked workitem when your code is also in Azure devops then when your code is in Github.

[rfennell]

Yes, given the lack of a formal API to get this information, as I said have to rely on string matching in messages. Sorry I think it is the best I can do