Jenkins Pipelines as Code with Jenkinsfile

Click-built Jenkins jobs do not scale or version. A Jenkinsfile puts your whole pipeline in source control, reviewed like any other code.

Declarative pipelines

Define stages, steps and post-actions in one file that lives with the application, so the pipeline evolves with the code.

A starter Jenkinsfile

Build, test and deploy as explicit, ordered stages.

pipeline {
  agent any
  stages {
    stage('Build') { steps { sh 'docker build -t app .' } }
    stage('Test')  { steps { sh 'make test' } }
    stage('Deploy'){ steps { sh './deploy.sh' } }
  }
}

Shared libraries

Extract common logic into a shared library so every team pipeline stays DRY and consistent, and a fix lands everywhere at once.

Wrapping Up

Pipeline as code makes Jenkins reproducible, reviewable and portable across teams.