Difference between revisions of "Continuous Integration: Tagging Jenkins Pipeline"
From Gcube Wiki
Manuele.simi (Talk | contribs) (Created page with "= 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.d4scie...") |
Manuele.simi (Talk | contribs) (→gCubeTagging Pipeline Project) |
||
| Line 2: | Line 2: | ||
In gCube we use a Pipeline to tag all the repositories forming a gCube Release. The pipeline project is available at: | 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- | + | https://jenkins.d4science.org/job/gCube-Tagging/ |
| + | |||
| + | |||
| + | |||
| + | == Parameters== | ||
| + | [[File:Jenkins_tagging_pipeline_params.png|800px]] | ||
| + | |||
| + | == Triggers == | ||
| + | No triggers are defined because the pipeline is expected to be manually launched by the [[Continuous_Integration:_Releases_Manager|Release Manager]]: | ||
| + | |||
| + | [[File:Jenkins_tagging_pipeline_triggers.png|400px]] | ||
| + | |||
| + | 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. | ||
| + | |||
| + | [[File:Jenkins_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.
