Continuous Integration: Notes Jenkins Pipeline
From Gcube Wiki
Revision as of 05:30, 12 July 2020 by Manuele.simi (Talk | contribs) (Created page with "= Release Notes Pipeline = \ This is the expected action plan: # the developer must add a related section to CHANGELOG.md *before* each release. The section must be compliant...")
Release Notes Pipeline
\ This is the expected action plan:
- the developer must add a related section to CHANGELOG.md *before* each release. The section must be compliant with the template
- upon the reception of the release ticket, the release manager checks and validates the changelog section for the component
- the release pipeline may enforce the presence of the changelog.md and of a section related to the current version of the artifact (i.e. it fails if both conditions are not matched)
- the tagging pipeline may create an aggregated changelog, with all the sections from the single changelogs...and send it to "Someone" in charge of creating the release notes.
- "Someone" elaborates the changelogs, merges them and produces a narrative for each major feature across all the released component.
WORK IN PROGRESS, TO BE COMPLETED AND DOCUMENTED
Back to the CI guide.