Difference between revisions of "Continuous Integration: Releases Jenkins Pipeline"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Triggers) |
Manuele.simi (Talk | contribs) |
||
| Line 3: | Line 3: | ||
= Jenkins Pipeline = | = Jenkins 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). | 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 [[Jenkins_Projects_(aka_Jobs)|jobs]] forming a gCube Release. The pipeline project is available at: | In gCube we use a Pipeline to trigger the builds of [[Jenkins_Projects_(aka_Jobs)|jobs]] forming a gCube Release. The pipeline project is available at: | ||
Revision as of 17:12, 29 May 2019
Contents
Jenkins 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
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
Jenkins Pipeline Definition
Back to the CI guide.
