Difference between revisions of "Continuous Integration: Releases Manager"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Responsibilities) |
Manuele.simi (Talk | contribs) |
||
Line 18: | Line 18: | ||
<nowiki>https://code-repo.d4science.org/gCubeCI/gCubeRelease/raw/branch/master/releases/<gcube_release_version>/tags.<report_number>.csv</nowiki>. | <nowiki>https://code-repo.d4science.org/gCubeCI/gCubeRelease/raw/branch/master/releases/<gcube_release_version>/tags.<report_number>.csv</nowiki>. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Revision as of 04:40, 30 December 2019
Responsibilities
The Release Manager is in charge of:
- Declaring when a gCube release is open and when it is closed
- Preparing the release file for each new gCube release
- Launching the build of the gCube Release Pipeline
- Storing the commits report generated by the gCube Release Pipeline in its Gitea repository
- Launching the build of the gCube Tagging Pipeline
- Storing the tag report generated by the gCube Tagging Pipeline in its Gitea repository
Pipeline Reports on Git
The Release Manager is responsible for manually pushing the reports generated by the jenkins pipelines to Git.
The build commits report generated by the gCube Release Pipeline must be stored in the pipeline git repository as
https://code-repo.d4science.org/gCubeCI/gCubeRelease/raw/branch/master/releases/<gcube_release_version>/build_commits.<report_number>.csv.
The tag report generated by the gCube Tagging Pipeline must be stored in the pipeline git repository as
https://code-repo.d4science.org/gCubeCI/gCubeRelease/raw/branch/master/releases/<gcube_release_version>/tags.<report_number>.csv.
Back to the CI guide.