Difference between revisions of "Continuous Integration: Releases Jenkins Pipeline"

From Gcube Wiki
Jump to: navigation, search
(Jenkins Pipeline)
(Jenkins Pipeline Definition)
Line 19: Line 19:
  
 
= Jenkins Pipeline Definition =
 
= Jenkins Pipeline Definition =
 +
 +
== Requirements==
 +
* [https://jenkins.io| Jenkins] ver. 2.164.2 or newer
 +
* [https://plugins.jenkins.io/workflow-aggregator| Pipeline Plugin]
 +
* [https://plugins.jenkins.io/workflow-basic-steps| Pipeline: Basic Steps]
 +
* [https://plugins.jenkins.io/pipeline-maven| Pipeline: Maven]
 +
* Jenkins configured with a JDK named 'OpenJDK 8'
 +
 +
  
 
''Back to the [[Continuous_Integration_procedure_(2019) | CI guide]].''
 
''Back to the [[Continuous_Integration_procedure_(2019) | CI guide]].''

Revision as of 17:19, 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).

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

Jenkins pipeline params.png

Triggers

No triggers are defined because the pipeline is designed to be manually launched by the Release Manager:

Jenkins pipeline triggers.png

Git

Jenkins pipeline git.png

Jenkins Pipeline Definition

Requirements


Back to the CI guide.