-
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
Generate Release Notes (Crossplatform) append feature not working #853
Comments
I cannot repo your problem, I have re-tested the append function and it is working for me. If you do a run with diagnostics on (for a variable
What does yours show? |
Hi , I am getting below logs:-
As you said I am getting |
That is strange, I will re-run my tests with a build as opposed to my test harness, but it looks like it should be working. The logic is not complex and logs show it is taking the route I expect. An alternative is to not use the append, just generate the file and do the merge with my WIKIUpdater Extension though is only of use if your target is a WIKI |
I have had a look at the code again, and is it possible that it is adding the appended content, but if stripping off the fit character so that heading just become standard text, thus looking as if it all merged together e.g.
as opposed to
The reason I ask is this was a recently fixed issue with prepend/append functionality for the WIKIUpdater #826 . If this is the case I can made the same change to this task to handle unexpected leading special characters |
No this is not the case , I am not even getting single line of older release notes. I also have one question does release notes output file generated by this task every time. if yes, how you are keeping track of old release notes and appending it in newly generated release notes file. |
Stranger and stranger.... As I cannot get a repo of this problem, and I have tried in both my release pipelines, my test harnesses and debugging in VSCode, all I can think to do to debug it further is for you to either
In answer to your second question, the most common usage of the task, from the feedback I have had from users, is that they generate the release notes for the build/release as a new file. This details just the changes since the last successful release. This file is then
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Generate Release Notes (Crossplatform) append feature not working.
Version: 3.23.2.
Below is yml code which I am using in azure pipeline
task: XplatGenerateReleaseNotes@3
inputs:
outputfile: '$(System.DefaultWorkingDirectory)/releasenotes.md'
templateLocation: 'InLine'
inlinetemplate: |
# Notes for release {{releaseDetails.releaseDefinition.name}}
**Environment: '$(env-type)'
Release Number : {{releaseDetails.name}}
Release completed : {{releaseDetails.modifiedOn}}
Build Number: {{buildDetails.id}}
Compared Release Number : {{compareReleaseDetails.name}}
Build Trigger PR Number: {{lookup buildDetails.triggerInfo 'pr.number'}}
dumpPayloadToConsole: false
dumpPayloadToFile: false
replaceFile: false
appendToFile: true
getParentsAndChildren: false
getAllParents: false
The text was updated successfully, but these errors were encountered: