Difference between revisions of "Continuous Integration: Releases Manager"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Responsibilities) |
Manuele.simi (Talk | contribs) (→Type of Builds) |
||
| Line 15: | Line 15: | ||
== Type of Builds == | == Type of Builds == | ||
| − | + | The Pipeline project can be launched in 4 different ways (Type parameter): | |
* SNAPSHOT-DRY-RUN (default) | * SNAPSHOT-DRY-RUN (default) | ||
| + | : with this build, ... | ||
* SNAPSHOT | * SNAPSHOT | ||
| + | : with this build, ... | ||
* RELEASE-DRY-RUN | * RELEASE-DRY-RUN | ||
| + | : with this build, ... | ||
* RELEASE | * RELEASE | ||
| + | : with this build, ... | ||
= Pipeline Activities = | = Pipeline Activities = | ||
''Back to the [[Continuous_Integration_procedure_(2019) | CI guide]].'' | ''Back to the [[Continuous_Integration_procedure_(2019) | CI guide]].'' | ||
Revision as of 18:23, 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
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.
