Difference between revisions of "Continuous Integration: Releases Manager"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Type of Builds) |
Manuele.simi (Talk | contribs) (→Type of Build) |
||
| Line 16: | Line 16: | ||
== Type of Build == | == Type of Build == | ||
| − | The Pipeline project can be launched in 4 different ways (Type parameter): | + | The Pipeline project can be launched in 4 different ways (''Type'' parameter): |
* SNAPSHOT-DRY-RUN (default) | * SNAPSHOT-DRY-RUN (default) | ||
: build snapshot artifacts, install the artifacts in a local repo, do not deploy | : build snapshot artifacts, install the artifacts in a local repo, do not deploy | ||
| Line 26: | Line 26: | ||
: build snapshot artifacts, install the artifacts in a local repo, deploy the artifacts to the ''gcube-releases'' Maven Repository | : 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 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. |
= 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:31, 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 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.
Pipeline Activities
Back to the CI guide.
