Difference between revisions of "Continuous Integration: Releases Manager"

From Gcube Wiki
Jump to: navigation, search
(Responsibilities)
 
Line 4: Line 4:
 
* Preparing the [[Continuous_Integration:_Releases_Jenkins_Pipeline#Jenkins_Pipeline_Configuration| release file]] for each new gCube release
 
* 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]]
 
* Launching the build of the [[Continuous_Integration:_Releases_Jenkins_Pipeline| gCube Release Pipeline]]
* Storing the commits report generated by the gCube Release Pipeline in its Gitea repository
+
* Storing the commits report generated by the gCube Release Pipeline in the [https://code-repo.d4science.org/gCubeCI/gCubeRelease Gitea repository] under the ''releases/<release number>'' folder
 
* Launching the build of the [[Continuous_Integration:_Releases_Jenkins_Pipeline| gCube Tagging Pipeline]]
 
* Launching the build of the [[Continuous_Integration:_Releases_Jenkins_Pipeline| gCube Tagging Pipeline]]
* Storing the tag report generated by the gCube Tagging Pipeline in its Gitea repository
+
* Storing the tag report generated by the gCube Tagging Pipeline in the [https://code-repo.d4science.org/gCubeCI/gCubeRelease Gitea repository] under the ''releases/<release number>'' folder
  
 
= Pipeline Reports on Git =
 
= Pipeline Reports on Git =

Latest revision as of 18:10, 13 January 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/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.