Difference between revisions of "Continuous Integration: Releases Jenkins Pipeline"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Jenkins Pipeline Definition) |
Manuele.simi (Talk | contribs) (→Git) |
||
Line 16: | Line 16: | ||
== Git == | == Git == | ||
+ | The [[Continuous_Integration:_Releases_Jenkins_Pipeline#Jenkins_Pipeline_Definition| pipeline definition]] is maintained in a Git repository. This section connects the project to the Git repository. | ||
[[File:Jenkins_pipeline_git.png|800px]] | [[File:Jenkins_pipeline_git.png|800px]] | ||
Revision as of 17:21, 29 May 2019
Jenkins Pipeline is a combination of plugins that support the integration and implementation of continuous delivery pipelines using Jenkins. A pipeline has an extensible automation server for creating simple or complex delivery pipelines "as code," via pipeline DSL (Domain-specific Language).
Contents
gCubeRelease Pipeline Project
In gCube we use a Pipeline to trigger the builds of jobs forming a gCube Release. The pipeline project is available at: https://jenkins.d4science.org/job/gCube-Release/
Parameters
Triggers
No triggers are defined because the pipeline is designed to be manually launched by the Release Manager:
Git
The pipeline definition is maintained in a Git repository. This section connects the project to the Git repository.
Jenkins Pipeline Definition
Requirements
- Jenkins ver. 2.164.2 or newer
- Pipeline Plugin
- Pipeline: Basic Steps
- Pipeline: Maven
- Jenkins configured with a JDK named 'OpenJDK 8'
Back to the CI guide.