Difference between revisions of "Continuous Integration: Tagging Jenkins Pipeline"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Parameters) |
Manuele.simi (Talk | contribs) (Undo revision 33787 by Manuele.simi (talk)) |
||
Line 7: | Line 7: | ||
== Parameters== | == Parameters== | ||
− | [[File:Jenkins_action_pipeline_params.png| | + | [[File:Jenkins_action_pipeline_params.png|400px]] |
== Triggers == | == Triggers == |
Revision as of 04:44, 26 January 2021
Contents
gCubeTagging Pipeline Project
A pipeline to execute configurable actions over a list of Git repositories:
The pipeline project is available at: https://jenkins.d4science.org/job/Pipeline-gCubeActions/
Parameters
Triggers
No triggers are defined because the pipeline is expected to be manually launched by the Release Manager:
Git
The pipeline is maintained in a Git repository. This section connects the project to the Git repository.
Jenkins Pipeline Definition
Git Repository
The definition of the gCube release pipeline is maintained in this Git Repository: ...
Requirements on Jenkins
Jenkins Pipeline Execution
Action Report
If the pipeline execution succeeds, it sends a tag report to the release manager. The report includes the following information for each Git repository tagged:
- the repo name
- the SCM url
- the result (completed or failed)
Here's an example of a tag report:
Back to the CI guide.