Difference between revisions of "Continuous Integration: Tagging Jenkins Pipeline"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Parameters) |
Manuele.simi (Talk | contribs) (→Parameters) |
||
| Line 8: | Line 8: | ||
== Parameters== | == Parameters== | ||
| − | [[File:Jenkins_tagging_pipeline_params.png| | + | [[File:Jenkins_tagging_pipeline_params.png|400px]] |
== Triggers == | == Triggers == | ||
Revision as of 04:32, 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.
