Continuous Integration: Tagging Jenkins Pipeline
Contents
gCubeTagging Pipeline Project
In gCube we use a Pipeline to tag all the repositories forming a gCube Release. The pipeline project is available at: https://jenkins.d4science.org/job/gCube-Tagging/
Parameters
Triggers
No triggers are defined because the pipeline is expected to be manually launched by the Release Manager:
It can be changed according to the release needs and the availability of a sufficient number of dedicate agents in Jenkins.
Git
The pipeline is maintained in a Git repository. This section connects the project to the Git repository.
Jenkins Pipeline Execution
Build with parameters...
Sample commit report:
On the jenkins console, we can see the messages logging the tagging activity on the repository:
On gitea, we can appreciate that the tag has been pushed;
On a local cloned repo, we can fetch the new tag:
