Difference between revisions of "Continuous Integration: Tagging Jenkins Pipeline"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→gCubeTagging Pipeline Project) |
Manuele.simi (Talk | contribs) (→Git) |
||
| Line 19: | Line 19: | ||
The pipeline is maintained in a Git repository. This section connects the project to the Git repository. | The pipeline is maintained in a Git repository. This section connects the project to the Git repository. | ||
| − | [[File: | + | [[File:Jenkins_tagging_pipeline_git.png|800px]] |
Revision as of 04:31, 23 December 2019
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.
