Difference between revisions of "Continuous Integration: Tagging Jenkins Pipeline"
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) (→Jenkins Pipeline Execution) |
||
| Line 23: | Line 23: | ||
= Jenkins Pipeline Execution = | = Jenkins Pipeline Execution = | ||
| + | Build with parameters... | ||
| − | + | Sample commit report: | |
| − | [[File:Jenkins_tagging_pipeline_gitea.png| | + | |
| + | On the jenkins console, we can see the messages logging the tagging activity on the repository: | ||
| + | |||
| + | [[File:Jenkins_tagging_pipeline_console.png|600px]] | ||
| + | |||
| + | On gitea, we can appreciate that the tag has been pushed; | ||
| + | |||
| + | [[File:Jenkins_tagging_pipeline_gitea.png|600px]] | ||
| + | |||
| + | On a local cloned repo, we can fetch the new tag: | ||
| + | |||
| + | [[File:Jenkins_tagging_pipeline_repo.png|600px]] | ||
Revision as of 05:37, 23 December 2019
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:
