Difference between revisions of "Continuous Integration: Notes Jenkins Pipeline"

From Gcube Wiki
Jump to: navigation, search
(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...")
 
 
Line 1: Line 1:
 
= Release Notes Pipeline =
 
= Release Notes Pipeline =
\
+
 
This is the expected action plan:
+
Available at https://jenkins.d4science.org/job/Pipeline-gCubeReleaseNotes/
 +
 
 +
== Procedure ==
  
 
# the developer must add a related section to CHANGELOG.md *before* each release. The section must be compliant with the template
 
# the developer must add a related section to CHANGELOG.md *before* each release. The section must be compliant with the template

Latest revision as of 22:59, 23 September 2020

Release Notes Pipeline

Available at https://jenkins.d4science.org/job/Pipeline-gCubeReleaseNotes/

Procedure

  1. the developer must add a related section to CHANGELOG.md *before* each release. The section must be compliant with the template
  2. upon the reception of the release ticket, the release manager checks and validates the changelog section for the component
  3. 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)
  4. 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.
  5. "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.