Why CI/CD pipeline basics in Spring Boot? - Purpose & Use Cases

The Big Idea

What if your code could build, test, and deploy itself every time you save a change?

The Scenario

Imagine you have a Spring Boot app and every time you make a change, you manually build the app, run tests, and then deploy it to your server by copying files one by one.

The Problem

This manual way is slow and tiring. You might forget a step, make mistakes, or deploy broken code. It's like baking a cake without a recipe and hoping it turns out right every time.

The Solution

A CI/CD pipeline automates building, testing, and deploying your Spring Boot app. It runs every time you change your code, so you catch errors early and deliver updates fast and safely.

Before vs After

✗ Before

git pull
./mvnw clean package
scp target/app.jar server:/apps/
ssh server 'systemctl restart app'

✓ After

pipeline {
  agent any
  stages {
    stage('Build') { steps { sh './mvnw clean package' } }
    stage('Test') { steps { sh './mvnw test' } }
    stage('Deploy') { steps { sh 'deploy-script.sh' } }
  }
}

What It Enables

It lets you deliver new features and fixes quickly and confidently, like having a trusted robot helper that never misses a step.

Real Life Example

A team working on a Spring Boot web app uses CI/CD to automatically test and deploy updates every time they push code, so users get improvements without waiting.

Key Takeaways

Manual deployment is slow and error-prone.

CI/CD pipelines automate build, test, and deploy steps.

This leads to faster, safer software delivery.

Practice

1. What is the main purpose of a CI/CD pipeline in a Spring Boot project?

easy

A. To automate building, testing, and deploying the application

B. To write the application code manually

C. To design the user interface of the application

D. To manage database schemas manually

Solution

1. Step 1: Understand CI/CD pipeline role

   A CI/CD pipeline automates repetitive tasks like building, testing, and deploying software.

2. Step 2: Match with Spring Boot context

   In Spring Boot projects, this automation helps deliver updates faster and catch errors early.

3. Final Answer:

   To automate building, testing, and deploying the application -> Option A

4. Quick Check:

   CI/CD pipeline = automation of build, test, deploy [OK]

Hint: CI/CD means automate build, test, deploy steps [OK]

Common Mistakes:

• Confusing CI/CD with coding or UI design
• Thinking CI/CD manages database manually
• Assuming CI/CD replaces writing code

2. Which of the following is the correct syntax to define a stage in a Jenkins pipeline for building a Spring Boot app?

easy

A. step('Build') { execute 'mvn clean package' }

B. buildStage { run 'mvn clean package' }

C. pipelineStage('Build') { shell 'mvn clean package' }

D. stage('Build') { steps { sh 'mvn clean package' } }

Solution

1. Step 1: Recall Jenkins pipeline syntax

   Jenkins uses stage('Name') { steps { ... } } to define stages.

2. Step 2: Verify correct command inside steps

   The shell command sh 'mvn clean package' is correct for building a Spring Boot app with Maven.

3. Final Answer:

   stage('Build') { steps { sh 'mvn clean package' } } -> Option D

4. Quick Check:

   Jenkins stage syntax = stage + steps + sh [OK]

Hint: Jenkins stages use stage('name') with steps block [OK]

Common Mistakes:

• Using incorrect keywords like buildStage or pipelineStage
• Missing steps block inside stage
• Using run or execute instead of sh for shell commands

3. Given this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'mvn test'
      }
    }
  }
}

What will happen when this pipeline runs?

medium

A. It builds the application without testing

B. It runs Maven tests and reports results

C. It deploys the application to production

D. It fails because 'mvn test' is invalid

Solution

1. Step 1: Analyze the pipeline stage

   The stage named 'Test' runs the shell command mvn test, which executes tests in Maven.

2. Step 2: Understand the pipeline effect

   Running mvn test triggers tests and generates test reports if any.

3. Final Answer:

   It runs Maven tests and reports results -> Option B

4. Quick Check:

   mvn test = run tests [OK]

Hint: mvn test runs tests, not build or deploy [OK]

Common Mistakes:

• Confusing test stage with build or deploy
• Thinking 'mvn test' is invalid command
• Assuming deployment happens automatically

4. You wrote this Jenkins pipeline snippet:

stage('Build') {
  sh 'mvn clean package'
}

But Jenkins shows an error. What is the likely cause?

medium

A. Missing steps block inside the stage

B. Wrong shell command syntax

C. Agent not specified in pipeline

D. Maven is not installed on Jenkins server

Solution

1. Step 1: Check Jenkins stage syntax

   Each stage must contain a steps { ... } block to run commands.

2. Step 2: Identify missing steps block

   The snippet lacks steps { }, causing Jenkins syntax error.

3. Final Answer:

   Missing steps block inside the stage -> Option A

4. Quick Check:

   Jenkins stage needs steps block [OK]

Hint: Always wrap commands inside steps { } in Jenkins stage [OK]

Common Mistakes:

• Omitting steps block inside stage
• Assuming shell command syntax is wrong
• Ignoring agent requirement (not error here)

5. You want to create a Jenkins pipeline that builds, tests, and deploys a Spring Boot app only if tests pass. Which pipeline structure achieves this?

hard

A. pipeline {
agent any
stages {
stage('Build') { steps { sh 'mvn clean package' } }
stage('Deploy') { steps { sh './deploy.sh' } }
stage('Test') { steps { sh 'mvn test' } }
}
}

B. pipeline {
agent any
stages {
stage('Test') { steps { sh 'mvn test' } }
stage('Deploy') { steps { sh './deploy.sh' } }
stage('Build') { steps { sh 'mvn clean package' } }
}
}

C. pipeline {
agent any
stages {
stage('Build') { steps { sh 'mvn clean package' } }
stage('Test') { steps { sh 'mvn test' } }
stage('Deploy') { steps { sh './deploy.sh' } }
}
}

D. pipeline {
agent any
stages {
stage('Deploy') { steps { sh './deploy.sh' } }
stage('Build') { steps { sh 'mvn clean package' } }
stage('Test') { steps { sh 'mvn test' } }
}
}

Solution

1. Step 1: Understand stage order importance

   Build must happen before testing, and deploy only after tests pass.

2. Step 2: Check pipeline stage sequence

   pipeline { agent any stages { stage('Build') { steps { sh 'mvn clean package' } } stage('Test') { steps { sh 'mvn test' } } stage('Deploy') { steps { sh './deploy.sh' } } } } has Build, then Test, then Deploy in correct order ensuring deploy runs only if tests succeed.

3. Final Answer:

   Build, Test, then Deploy in sequence -> Option C

4. Quick Check:

   Correct stage order ensures safe deploy [OK]

Hint: Deploy only after successful test stage [OK]

Common Mistakes:

• Deploying before tests run
• Running tests after deploy
• Incorrect stage order breaking pipeline logic