-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to increase the number of workitems and commits from default 50 to more number while using Releasenote generation Cross platform #804
Comments
I tried adding a variable in the build pipeline ReleaseNotes.Fix349 to true but it is still showing the same result.Its only picking first 50 WorkItems and first 50 commits etc The below shown is a portion of the log details of the run task. For the record we are using Inline handlebar template in ReleaseNote crossplatform Get details of [50] WIs please advice |
Another issue that i have noticed is that while running the Generate release notes (PowerShell) and Generate Release Notes (Crossplatform) in the same build Iam obtaining entirely different workitems and commits with no correlation to each other |
I will have to setup a test with enough WI and Commits, might be a few days before I get around to it, but I will have a look I am not surprised the lists are different, they use different logic.
|
Ok thanks for the update.Hoping to get a reply soon |
Turns out there is a code path that did not make use of the #349 style fix in the new YAML pipeline specific code. The calls made do default to 50 items, I have altered these to 5000. I am currently testing a new release it will be 3.11.x |
I want to increase the number of workitems and commits obtained by the Releasenote (Crossplatform) in a build from the default set value of 50 to atleast 200 each for workitems and commits
Iam using the handlebar syntax as follows
#Release Note
Associated WorkItems ({{workItems.length}})
{{#each workItems}}
{{/each}}
Associated commits ({{commits.length}})
{{#each commits}}
{{/each}}
The text was updated successfully, but these errors were encountered: