Difference between revisions of "Continuous Integration: Releases Manager"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Responsibilities) |
Manuele.simi (Talk | contribs) (→Monitor the Execution) |
||
Line 30: | Line 30: | ||
== Monitor the Execution == | == Monitor the Execution == | ||
+ | At least one “stage” section must be defined on the “stages” section of the pipeline. It will contain the work that the pipeline will execute. Stages must be named accordingly since Jenkins will display each of them on its interface, as shown here: | ||
+ | |||
+ | [[File:CI_Pipeline_Execution.png|600px]] | ||
== Report == | == Report == |
Revision as of 05:17, 30 May 2019
Contents
Responsibilities
The Release Manager is in charge of:
- Declaring when a gCube release is open and when it is closed
- Launching the build of the gCube Pipeline
- Maintaining the Pipeline Definition
Jenkins Activities
Launch the Pipeline
In Jenkins:
- select the gCubeRelease project
- on the left side, click on 'Build with Parameters'
- select the type of build we want to generate in the choice menu
- click on the 'Build' button
Type of Build
The Pipeline project can be launched in 4 different ways (Type parameter):
- SNAPSHOT-DRY-RUN (default)
- build snapshot artifacts, install the artifacts in a local repo, do not deploy
- SNAPSHOT
- build snapshot artifacts, install the artifacts in a local repo, deploy the artifacts to the gcube-snapshots Maven Repository
- RELEASE-DRY-RUN
- build release artifacts, install the artifacts in a local repo, do not deploy
- RELEASE
- build snapshot artifacts, install the artifacts in a local repo, deploy the artifacts to the gcube-releases Maven Repository
The idea behind these builds is that the Release Manager can test the full pipeline execution with the DRY-RUN builds. Once all the projects in the build work, the SNAPSHOT or RELEASE build can be launched to effectively deploy the artifacts on the remote Maven Repository.
Monitor the Execution
At least one “stage” section must be defined on the “stages” section of the pipeline. It will contain the work that the pipeline will execute. Stages must be named accordingly since Jenkins will display each of them on its interface, as shown here:
Report
Pipeline Activities
Back to the CI guide.