Getting started with Pipeline | jenkins pipeline tool
RelevantcomponentsofGroovysyntaxwillbeintroducedasrequiredthroughoutthisdocumentation,sowhileanunderstandingofGroovyishelpful,itisnotrequiredtoworkwithPipeline.APipelinecanbecreatedinoneofthefollowingways:ThroughBlueOcean[1]-aftersettingupaPipelineprojectinBlueOcean,theBlueOceanUIhelpsyouwriteyourPipeline’sJenkinsfileandcommitittosourcecontrol.ThroughtheclassicUI[2]-youcanenterabasicPipelinedirectlyinJenkinsthroughtheclassicUI.InSCM[3]-youcanwriteaJenkinsfilemanually,whichyoucancommittoyourp...
Relevant components of Groovy syntax will be introduced as required throughout this documentation, so while an understanding of Groovy is helpful, it is not required to work with Pipeline.
A Pipeline can be created in one of the following ways:
Through Blue Ocean[1] - after setting up a Pipeline project in Blue Ocean, the Blue Ocean UI helps you write your Pipeline’s Jenkinsfile and commit it to source control.
Through the classic UI[2] - you can enter a basic Pipeline directly in Jenkins through the classic UI.
In SCM[3] - you can write a Jenkinsfile manually, which you can commit to your project’s source control repository.
The syntax for defining a Pipeline with either approach is the same, but while Jenkins supports entering Pipeline directly into the classic UI, it is generally considered best practice to define the Pipeline in a Jenkinsfile which Jenkins will then load directly from source control.
Through Blue Ocean