Project 2 — CI Pipeline with Jenkinsfile

Goal

Move from UI Freestyle jobs to Pipeline as Code. Build a Node.js Express project with install → test → PM2 deploy → email.

Sample path in the course repo:

https://github.com/VenkatMastercoder/jenkins-cicd-projects/tree/master/project-2-pipeline-jenkinsfile

App structure

project-2-pipeline-jenkinsfile/
├── .gitignore
├── index.js
├── index.test.js
├── Jenkinsfile
├── package-lock.json
└── package.json

Example Jenkinsfile

pipeline {
  agent any
 
  environment {
    PROJECT_DIR = "project-2-pipeline-jenkinsfile"
    PM2_APP_NAME = "project-2-app"
    EMAIL_TO = "your-email@gmail.com"
  }
 
  stages {
    stage('Preparation') {
      steps {
        sh '''
          echo "Build started!"
          echo "Branch: ${GIT_BRANCH}"
          echo "Build Number: ${BUILD_NUMBER}"
          ls -la
        '''
      }
    }
 
    stage('Install Dependencies') {
      steps {
        dir("${PROJECT_DIR}") {
          sh 'npm install'
        }
      }
    }
 
    stage('Run Tests') {
      steps {
        dir("${PROJECT_DIR}") {
          sh 'npm test'
        }
      }
    }
 
    stage('Deploy with PM2') {
      when {
        expression { currentBuild.currentResult == 'SUCCESS' }
      }
      steps {
        dir("${PROJECT_DIR}") {
          sh '''
            export PATH=$PATH:/usr/local/bin
            echo "Deploying app using PM2..."
 
            if pm2 list | grep -q "${PM2_APP_NAME}"; then
              echo "App exists -> Restarting..."
              pm2 restart "${PM2_APP_NAME}"
            else
              echo "App not found -> Starting..."
              pm2 start index.js --name "${PM2_APP_NAME}"
            fi
 
            pm2 save
          '''
        }
      }
    }
  }
 
  post {
    always {
      script {
        def buildStatus = currentBuild.currentResult ?: 'UNKNOWN'
        mail(
          to: "${EMAIL_TO}",
          subject: "Jenkins Build ${buildStatus}: ${env.JOB_NAME} #${env.BUILD_NUMBER}",
          body: """Build Notification
 
Job: ${env.JOB_NAME}
Build: #${env.BUILD_NUMBER}
Branch: ${env.GIT_BRANCH}
Status: ${buildStatus}
URL: ${env.BUILD_URL}"""
        )
      }
    }
  }
}

Update EMAIL_TO to your address. SMTP must already be configured from the post-build lesson.

Prerequisites

• Jenkins running (EC2 + Docker)
• Node.js and PM2 installed inside the Jenkins container (previous lesson)
• GitHub credentials configured
• Email / SMTP set up

Step 1 — Create a Pipeline job

1. Dashboard → New Item
2. Name: project-2-pipeline
3. Select Pipeline → OK

Step 2 — Pipeline script from SCM

1. Definition: Pipeline script from SCM

2. SCM: Git
3. Repository URL: https://github.com/VenkatMastercoder/jenkins-cicd-projects.git
4. Select credentials
5. Branch: */master (or */main)
6. Script Path: project-2-pipeline-jenkinsfile/Jenkinsfile
7. Save

Step 3 — Build

Click Build Now. Watch stages: Preparation → Install → Test → Deploy.

Open Console Output or the stage view if Blue Ocean / stage UI is available.

Step 4 — Optional: GitHub webhook (preview of Day 3)

1. Manage Jenkins → Plugins → install GitHub if missing
2. Job → Build Triggers → check GitHub hook trigger for GITScm polling
3. On GitHub: repo → Settings → Webhooks → Add webhook
   • Payload URL: http://<your-ec2-public-ip>:8080/github-webhook/
   • Content type: application/json
   • Events: Just the push event
4. Push a small commit — Jenkins should start automatically

What you achieved

Freestyle (UI)  →  Pipeline as Code (Jenkinsfile)
Install → Test → Deploy (PM2) → Email

Day 3 adds Docker build/push/deploy and hardens webhooks + credentials for a full CI/CD path.