Getting previous build pull request #1083
Replies: 3 comments 2 replies
-
Commits and WI are found based on any created/associated since the last successful running of the build definition. It is from these that a list of PRs are found (by looking for specific fields) You can see the logic being used if you set a variable You can upload the log here and I will have a look if you can't spot anything |
Beta Was this translation helpful? Give feedback.
-
That is the basic logging, it does not show all the debug details (you need the Anyway, your current build is associated with 5 commits. This information is found using the Azure DevOps REST API call
so this is nothing I have any control over it is the same call as used by the Azure DevOps UI
Each of these commits is associated with PR hence what is returned.
One thought, is this the first succesful running of this pipeline. If it is then you expect the release notes to call all past associated items in the repo |
Beta Was this translation helpful? Give feedback.
-
As I said I cannot offer any other suggestions as I get the associaed commits using the SDK API call which is in effect just the REST endpoint All I do is pass in the build ID and the list of associated commits is returned. These will match commits listed as associations with the Azure DevOps UI e.g this build is associated with 10 commits Obviously there could be an issue with my PR association logic, but as your log shows it find 5 commits, not 2, I don't think the issue is with the PRs but the the Commits. Maybe have a play with the API call in a browser to confirm what is being returned? |
Beta Was this translation helpful? Give feedback.
-
Hi ,
When i generate a new build to generate release notes it picked all the previous pull request. Ideally it should get only the pull requests associated with that particular build not all?
Could please let me know what setting is required for that?
Thanks!
Regards,
Ashish
Beta Was this translation helpful? Give feedback.
All reactions