CI/CD pipeline basics in Spring Boot - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Jenkins pipeline stage?

Consider this Jenkins pipeline snippet for a Spring Boot project build stage. What will be the output after running the 'Build' stage?

Spring Boot

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'mvn clean package'
      }
    }
  }
}

A Build successful with a generated JAR file in target/ directory

B Build fails due to missing Dockerfile

C Build successful but no JAR file generated

D Pipeline syntax error stops execution

💡 Hint

Maven's 'clean package' command compiles and packages the Spring Boot app.

The 'mvn clean package' command cleans previous builds and packages the app, producing a JAR file in the target directory if successful.

🧠 Conceptual

intermediate

Which step is essential in a CI/CD pipeline for Spring Boot to ensure code quality?

In a typical CI/CD pipeline for a Spring Boot application, which step is crucial to catch bugs early before deployment?

A Running unit and integration tests after build

B Deploying directly to production without tests

C Manual code review only without automated tests

D Skipping build and deploying source code

💡 Hint

Automated tests help catch errors early in the pipeline.

Running automated tests after building ensures code quality and prevents faulty code from progressing to deployment.

❓ Troubleshoot

advanced

Why does this Jenkins pipeline fail at the deploy stage?

Given this Jenkins pipeline snippet, why does the deploy stage fail?

Spring Boot

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'mvn clean package'
      }
    }
    stage('Deploy') {
      steps {
        sh 'docker build -t springboot-app .'
        sh 'docker push springboot-app'
      }
    }
  }
}

A Deploy stage succeeds without errors

B Build fails because Maven command is incorrect

C Pipeline syntax error due to missing agent declaration

D Docker push fails because the image tag is incomplete or missing registry info

💡 Hint

Docker images usually require a full tag including registry or repository before push.

The 'docker push springboot-app' command fails because the image tag lacks registry or repository info, so Docker doesn't know where to push.

🔀 Workflow

advanced

What is the correct order of stages in a CI/CD pipeline for Spring Boot?

Arrange these stages in the correct order for a typical CI/CD pipeline:

A 1,3,2,4

B 2,1,3,4

C 1,2,3,4

D 3,1,2,4

💡 Hint

Tests should run after build and before deployment.

The pipeline builds the app first, then runs tests to verify it, then deploys to staging for validation, and finally to production.

✅ Best Practice

expert

Which practice improves CI/CD pipeline reliability for Spring Boot microservices?

To improve reliability and reduce downtime in CI/CD pipelines for Spring Boot microservices, which practice is best?

A Deploy all microservices simultaneously without testing

B Implement blue-green deployment to switch traffic between environments

C Skip automated tests to speed up deployment

D Manually update production servers without automation

💡 Hint

Blue-green deployment allows safe switching between versions.

Blue-green deployment reduces downtime by running two identical environments and switching traffic only after successful deployment.

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