Pipeline pipeline project is built by declarative and jenkinsfile under Jenkins

One 、Pipelin brief introduction

1. Concept

Pipeline, Simply speaking , Namely bash One set runs on Jenkins Workflow framework on , It will run independently on a single or multiple nodes Connect your tasks , To realize the complex process arrangement and visualization work that single task is difficult to complete .

2. Use Pipeline There are the following benefits （ From translation from official documents ）：

• Code ：Pipeline In the form of code , Usually checked into source code control , Enables the team to edit , Review and iterate its delivery process .
• persistent ： Whether it's a planned or unplanned server restart ,Pipeline It's all recoverable .
• Can stop ：Pipeline Can receive interactive input , To determine whether to proceed with Pipeline.
• multi-function ：Pipeline Support complex continuous delivery requirements in the real world . It supports fork/join、 Loop execution , The ability to perform tasks in parallel .
• Scalable ：Pipeline plug-in unit Support its DSL Custom extension for , And multiple options for integration with other plug-ins .

3. How to create Jenkins Pipeline Well

• Pipeline The script was created by Groovy The realization of language , But we don't have to study alone Groovy
• Pipeline Two kinds of grammar are supported ：Declarative( declarative ) and Scripted Pipeline( Scripted ) grammar
• Pipeline There are also two ways to create ： Can be directly in Jenkins Of Web UI Input script in the interface ; You can also create a individual Jenkinsfile The script file is put into the source library of the project （ Generally, we recommend Jenkins Directly from source control (SCM) Directly loaded in Jenkinsfile Pipeline This method ）.

Two 、 stay jenkins Install in Pipeline plug-in unit

After installing the plug-in , There's more time to create projects “ Assembly line ” type

3、 ... and 、 Create a pipeline project

1. Declarative declarative

• Create project ：
  
  
  The automatically generated script is as follows ：

• stages： Representing the whole assembly line All execution phases . Usually stages Only 1 individual , It contains more than one stage
• stage： Represents a stage in the pipeline , May appear n individual . It is generally divided into pull code , Compiling and constructing , Deployment and so on .
• steps： Represents the logic that needs to be executed in a phase .steps Inside is shell Script ,git Pull the code ,ssh Any content such as remote Publishing .
  

• Pull the code
  

• Deploy to tomcat
  

• The overall script is as follows ：

pipeline {
    
    agent any
     stages {
    
        stage ('pull code') {
    
            steps {
    
                checkout([$class: 'GitSCM', branches: [[name: '*/master']], extensions: [], userRemoteConfigs: [[credentialsId: '2121e63d-3284-4703-9cf7-4ccf9bc536c2', url: '[email protected]:xxxxx/jenkins_war.git']]])
            }
        }
        stage ('bulid project') {
    
          steps {
    
                sh 'mvn clean package'
            }
        }
        stage ('deploy to tomcat') {
    
         steps {
    
                deploy adapters: [tomcat9(credentialsId: '68a5c257-6180-4d44-be87-9dda0daf2ba5', path: '', url: 'http://10.10.10.14:8080/')], contextPath: null, war: 'target/*.war'
            }
        }
    }
}

• The console output is as follows
  
  

2. Pipeline Script from SCM（Jenkinsfile The way , It can be directly to Jenkinsfile Version control ） Recommended

Just now we were all directly in Jenkins Of UI Interface writing Pipeline Code , This is not convenient for script maintenance , Make a proposal to Pipeline Script placement
In the project （ Version control together ）

• Created in the project root directory Jenkinsfile file , Copy the contents into the file ,pull To remote warehouse

pipeline {
    
    agent any
     stages {
    
        stage ('pull code') {
    
            steps {
    
                checkout([$class: 'GitSCM', branches: [[name: '*/master']], extensions: [], userRemoteConfigs: [[credentialsId: '2121e63d-3284-4703-9cf7-4ccf9bc536c2', url: '[email protected]:xxxx/jenkins_war.git']]])
            }
        }
        stage ('bulid project') {
    
          steps {
    
                sh 'mvn clean package'
            }
        }
        stage ('deploy to tomcat') {
    
         steps {
    
                deploy adapters: [tomcat9(credentialsId: '68a5c257-6180-4d44-be87-9dda0daf2ba5', path: '', url: 'http://10.10.10.14:8080/')], contextPath: null, war: 'target/*.war'
            }
        }
    }
}

• New pipeline project
  
• Building again can also succeed

Reference video