Difference between revisions of "Continuous Integration: Releases Manager"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Jenkins Activities) |
Manuele.simi (Talk | contribs) (→Responsibilities) |
||
(24 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
= Responsibilities = | = Responsibilities = | ||
The Release Manager is in charge of: | The Release Manager is in charge of: | ||
− | * Launching the build of the [[Continuous_Integration:_Releases_Jenkins_Pipeline| gCube Pipeline]] | + | * Declaring when a gCube release is open and when it is closed |
− | * | + | * Preparing the [[Continuous_Integration:_Releases_Jenkins_Pipeline#Jenkins_Pipeline_Configuration| release file]] for each new gCube release |
+ | * Launching the build of the [[Continuous_Integration:_Releases_Jenkins_Pipeline| gCube Release Pipeline]] | ||
+ | * Storing the commits report generated by the gCube Release Pipeline in the [https://code-repo.d4science.org/gCubeCI/gCubeReleaseConfigs Gitea repository] under the ''releases/<release number>'' folder | ||
+ | * Launching the build of the [[Continuous_Integration:_Releases_Jenkins_Pipeline| gCube Tagging Pipeline]] | ||
+ | * Storing the tag report generated by the gCube Tagging Pipeline in the [https://code-repo.d4science.org/gCubeCI/gCubeReleaseConfigs Gitea repository] under the ''releases/<release number>'' folder | ||
− | = | + | = Pipeline Reports on Git = |
− | + | The Release Manager is responsible for manually pushing the reports generated by the jenkins pipelines to Git. | |
− | + | The [[Continuous_Integration:_Releases_Jenkins_Pipeline#Build_Commits_Report|build commits report]] generated by the gCube Release Pipeline '''must be stored''' in the pipeline [https://code-repo.d4science.org/gCubeCI/gCubeReleaseConfigs git repository] as | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | <nowiki>https://code-repo.d4science.org/gCubeCI/gCubeReleaseConfigs/raw/branch/master/releases/<gcube_release_version>/build_commits.<report_number>.csv</nowiki>. | |
− | + | The [[Continuous_Integration:_Tagging_Jenkins_Pipeline#Tag_Report|tag report]] generated by the gCube Tagging Pipeline '''must be stored''' in the pipeline [https://code-repo.d4science.org/gCubeCI/gCubeReleaseConfigs git repository] as | |
− | The Pipeline | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | : | + | |
− | + | <nowiki>https://code-repo.d4science.org/gCubeCI/gCubeReleaseConfigs/raw/branch/master/releases/<gcube_release_version>/tags.<report_number>.csv</nowiki>. | |
− | |||
− | + | ''Back to the [[Continuous_Integration_procedure_(2019) | CI guide]].'' | |
− | + | [[Category:Continuous_Integration]] | |
− | + | ||
− | + |
Latest revision as of 16:50, 22 May 2020
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 the Gitea repository under the releases/<release number> folder
- Launching the build of the gCube Tagging Pipeline
- Storing the tag report generated by the gCube Tagging Pipeline in the Gitea repository under the releases/<release number> folder
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/gCubeReleaseConfigs/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/gCubeReleaseConfigs/raw/branch/master/releases/<gcube_release_version>/tags.<report_number>.csv.
Back to the CI guide.