Pipeline and Jenkinsfile

• Achieve clear separation of concerns
• Easily spot failures and bottlenecks
• Parallelize independent tasks (e.g., linting alongside unit tests)

​

1. Writing Your Jenkinsfile

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'mvn clean package'
      }
    }
    stage('Unit Test') {
      steps {
        sh 'mvn test'
      }
    }
    stage('Dockerize') {
      steps {
        sh 'docker build -t myapp:${BUILD_NUMBER} .'
        sh 'docker push myapp:${BUILD_NUMBER}'
      }
    }
    stage('Deploy') {
      steps {
        sh 'kubectl apply -f deployment.yaml'
      }
    }
  }
}

​

2. Declarative vs. Scripted Pipelines

​

3. Pipeline vs. Freestyle Projects

​

4. Key Benefits of Jenkins Pipelines

1. Code as Configuration
   Version your Jenkinsfile alongside application code for audit trails and collaborative editing.
2. Resilience by Design
   Pipelines automatically resume after Jenkins controller restarts, preserving workflow state.
3. Human Interaction
   Pause for manual approvals, input parameters, or interactive prompts.
4. Advanced Workflow Control
   Use forks, joins, loops, and parallel stages to orchestrate complex CI/CD flows.
5. Extensibility
   Leverage plugins or Shared Libraries to add custom pipeline steps.
6. Unified Job Management
   Combine multiple build and deploy steps into a single Pipeline job, reducing maintenance overhead.

​

Links and References

• Jenkins Pipeline Syntax
• Declarative Pipeline Documentation
• Scripted Pipeline Overview
• Official Jenkins GitHub Repository
• Jenkins Shared Libraries