Difference between revisions of "Continuous Integration: Releases Manager"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Type of Builds) |
Manuele.simi (Talk | contribs) (→Launch the pipeline) |
||
| Line 8: | Line 8: | ||
In Jenkins: | In Jenkins: | ||
| − | + | # select the [[Continuous_Integration:_Releases_Jenkins_Pipeline#gCubeRelease_Pipeline_Project| 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 | ||
[[File:CI_ReleaseManager_launch.png|600px]] | [[File:CI_ReleaseManager_launch.png|600px]] | ||
Revision as of 18:24, 29 May 2019
Contents
Responsibilities
The Release Manager is in charge of:
- 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 Builds
The Pipeline project can be launched in 4 different ways (Type parameter):
- SNAPSHOT-DRY-RUN (default)
- with this build, ...
- SNAPSHOT
- with this build, ...
- RELEASE-DRY-RUN
- with this build, ...
- RELEASE
- with this build, ...
Pipeline Activities
Back to the CI guide.
