Difference between revisions of "Continuous Integration: Actions Jenkins Pipeline"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Action Report) |
Manuele.simi (Talk | contribs) (→Action Report) |
||
| Line 36: | Line 36: | ||
= Action Report = | = Action Report = | ||
| − | If the pipeline execution succeeds, it sends a | + | If the pipeline execution succeeds, it sends a report to the release manager. |
| − | The report includes the following information for each Git repository | + | |
| − | * | + | The report includes the following information for each Git repository where the action was executed: |
| − | * | + | * repo name |
| − | * | + | * SCM url |
| + | * result (completed or failed) | ||
Here's an example of a tag report: | Here's an example of a tag report: | ||
Revision as of 03:50, 26 January 2021
Contents
gCubeActions 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
- Git Root: The URL of the parent organization that includes all the listed repositories.
- List of Repositories: A plain text file, one line for each Git repository name to update.
- Action Root: The root URL of the Bash fragment to execute.
- Action File: The relative path under the Action Root of a Bash script
Example:
Triggers
No triggers are defined because the pipeline is expected to be manually launched by the Release Manager.
Jenkins Pipeline Definition
Git Repository
The definition of the gCube release pipeline is maintained in this Git Repository: ...
Requirements on Jenkins
- Jenkins ver. 2.164.2 or newer
- Pipeline Plugin
- Pipeline: Basic Steps
- Pipeline: Maven
- Pipeline: SCM Step plugin ver. 2.7 or newer
- Pipeline: Shared Groovy Libraries ver. 2.15 or newer
- User credentials configured on Jenkins. These are needed to set the author of the changes in the repositories. git.gcube is currently used
Jenkins Pipeline Execution
Action Report
If the pipeline execution succeeds, it sends a report to the release manager.
The report includes the following information for each Git repository where the action was executed:
- repo name
- SCM url
- result (completed or failed)
Here's an example of a tag report:
Back to the CI guide.
