Difference between revisions of "Continuous Integration: Releases Manager"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Launch the pipeline) |
Manuele.simi (Talk | contribs) (→Responsibilities) |
||
| 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]] |
| − | * | + | * Maintaining the [[Continuous_Integration:_Releases_Jenkins_Pipeline#Jenkins_Pipeline_Definition| Pipeline Definition]] |
= Jenkins Activities = | = Jenkins Activities = | ||
Revision as of 18:21, 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
Type of Builds
There are 4 types of builds that can be executed with the Pipeline:
- SNAPSHOT-DRY-RUN (default)
- SNAPSHOT
- RELEASE-DRY-RUN
- RELEASE
Pipeline Activities
Back to the CI guide.
