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

From Gcube Wiki
Jump to: navigation, search
Line 1: Line 1:
  
  
[[https://jenkins.io/doc/book/pipeline/| 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).
+
[https://jenkins.io/doc/book/pipeline/| 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 =
 
= gCubeRelease Pipeline Project =

Revision as of 16:22, 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

The pipeline definition is maintained in a Git repository. This section connects the project to the Git repository. Jenkins pipeline git.png

Jenkins Pipeline Definition

Requirements


Back to the CI guide.