Pipeline changes to generate and post release with release notes.#65
Pipeline changes to generate and post release with release notes.#65
Conversation
| script: """ | ||
| git log ${previousTag}..${params.TAG} --pretty=format:'* %s ([%h](https://github.com/VoltDB/volt-testcontainer/commit/%H))' --no-merges || echo "" | ||
| """ | ||
| ).trim() |
There was a problem hiding this comment.
It would be good to strip out any ENG-xxxxx[:] or Eng-xxxxx[:] prefixes from the commit messages.
There was a problem hiding this comment.
Thats why I have a option where pipeline can add custom message without tickets and commit logs.
This will allow us to provide our own message to post in release note.
|
I've thought about this and ultimately I don't see the value over using Github's auto-generated Release Notes. The formatting is very similar. I asked Claude to mock-up what they would look like. This PR's Jenkins-generated approach:
Note that the Pull Requests section would not even appear because there are no traditional merge commits, all PRs are squash-merged. Github auto-generated:
In either case, someone will need to edit the generated notes to remove ENG-xxxxx ticket numbers, omit test or process-oriented changes, and reword the commit messages (that weren't intended to be release notes). We can edit either way, whether we use the built-in Github auto-generation or this code, but if we just used Github, there's less code to maintain and less complexity during the release process, so I'm not seeing the value in doing this. |
See my previous comment |
2 participants
No description provided.