Continuous Integration: Releases
Releases in gCube are managed with Jenkins.
Single Jenkins jobs are triggered at each commit in the master branch for the Continuous Integration. Their outcomes are deployed on the Maven Snapshot Repository.
A dedicate Jenkins pipeline has been created to manage full builds of all the Jenkins jobs and to release the artifacts (i.e. deploy them on the Maven Release Repository) when successful. The pipeline is configured with a set of Maven build profiles to accommodate the different build scenarios.
Contents
Maven Build Profiles
A gCube artifact can be built in 3 different situations:
- on a personal (development) machine, likely after new code has been developed, by a gCube developer
- on a Jenkins slave, likely triggered by a new commit in the Git repository
- on a Jenkins slave, as part of the release pipeline
To support these scenarios, the following profiles are in the gCube maven-parent
https://code-repo.d4science.org/gCubeSystem/maven-parent
gcube-developer
- Dependencies resolved against gcube-snapshots and gcube-releases
- Snapshot artifacts deployed to gcube-snapshots
- Deployments of releases artifacts are not permitted
jenkins-snapshots
- Dependencies resolved against local-snapshots and gcube-releases
- Snapshot artifacts installed to local-snapshots
- Snapshot artifacts deployed to gcube-snapshots
- Deployments of release artifacts are not permitted
jenkins-releases
- Dependencies resolved against gcube-releases
- Deployments of snapshot artifacts are not permitted
- Release artifacts deployed to gcube-releases
dry-run
This profile disables the deployment of the artifacts.
disable-java8-doclint
This profile sets an additional parameter for javadoc generation to disables the doclint. It avoids the build fails if formal/syntax errors are found in javadoc comments.
Jenkins Pipeline
Jenkins Pipeline Definition
Activities of Release Manager
Back to the CI guide.