Build tools (Maven, Gradle, npm) in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this Maven build command?

You run the following command in a Jenkins pipeline:

mvn clean install -DskipTests

What will be the main effect of this command?

Jenkins

mvn clean install -DskipTests

A It cleans the project, compiles the code, packages it, and skips running tests.

B It only runs the tests without building the project.

C It installs dependencies but does not compile or package the project.

D It cleans the project and runs tests but does not package the code.

💡 Hint

The 'clean' phase removes previous build files, 'install' compiles and packages, and '-DskipTests' skips tests.

The 'mvn clean install' command cleans old files, compiles, runs tests, and packages the project. Adding '-DskipTests' skips the test execution but still compiles and packages.

❓ Configuration

intermediate

Which Gradle build script snippet correctly applies the Java plugin and sets the Java version to 17?

Choose the correct Gradle build script snippet to apply the Java plugin and set the Java source and target compatibility to version 17.

A

plugins {
    id 'java'
}

java {
    sourceCompatibility = '17'
    targetCompatibility = '17'
}

B

plugins {
    id 'java'
}

java {
    sourceCompatibility = JavaVersion.VERSION_17
    targetCompatibility = JavaVersion.VERSION_17
}

C

apply plugin: 'java'

sourceCompatibility = '1.7'
targetCompatibility = '1.7'

D

apply plugin: 'java'

java {
    sourceCompatibility = JavaVersion.VERSION_1_7
    targetCompatibility = JavaVersion.VERSION_1_7
}

💡 Hint

Use JavaVersion constants for version 17 and the plugins block for modern Gradle scripts.

Option B uses the plugins block and sets source and target compatibility to JavaVersion.VERSION_17, which is correct for Java 17. Other options either use old syntax or wrong versions.

🔀 Workflow

advanced

In a Jenkins pipeline, which npm command sequence correctly installs dependencies and runs tests with coverage?

You want to install npm dependencies and then run tests with coverage reporting in a Jenkins pipeline. Which command sequence is correct?

A npm install && npm run test:coverage

B npm run test:coverage && npm install

C npm test && npm install

D npm install test:coverage

💡 Hint

Dependencies must be installed before running tests.

Option A installs dependencies first, then runs the test script with coverage. Option A runs tests before installing, which fails. Option A runs tests without coverage and installs after. Option A is invalid syntax.

❓ Troubleshoot

advanced

What error will this Maven command produce if the pom.xml file is missing?

You run this command in a Jenkins job:

mvn clean package

But the pom.xml file is missing in the workspace. What error will Maven show?

Jenkins

mvn clean package

A [ERROR] Could not find the 'package' command.

B [ERROR] Missing Java compiler version in pom.xml.

C [ERROR] The goal you specified requires a project to execute but there is no POM in this directory.

D [ERROR] Network connection failed while downloading dependencies.

💡 Hint

Maven requires a pom.xml file to run goals like clean or package.

Without pom.xml, Maven cannot find project info and shows error about missing POM. Other errors relate to different issues.

✅ Best Practice

expert

Which npm script configuration in package.json ensures tests run only after dependencies are installed in Jenkins?

You want to configure your package.json scripts so that running npm run ci-test in Jenkins installs dependencies and then runs tests. Which scripts section is correct?

Jenkins

{
  "scripts": {
    "install": "npm install",
    "test": "jest",
    "ci-test": "???"
  }
}

A "ci-test": "npm test"

B "ci-test": "npm test && npm install"

C "ci-test": "npm install; npm test"

D "ci-test": "npm install && npm test"

💡 Hint

Tests should run after dependencies are installed; use && to chain commands.

Option D runs 'npm install' first, then 'npm test'. Option D runs tests before install, which can fail. Option D uses semicolon which works but is less safe in cross-platform scripts. Option D skips install.

Practice

1. What is the primary purpose of build tools like Maven, Gradle, and npm in Jenkins pipelines?

easy

A. To automate compiling, testing, and packaging code

B. To write application code manually

C. To deploy applications to production servers

D. To monitor server health and uptime

Solution

1. Step 1: Understand build tools' role

   Build tools automate tasks like compiling code, running tests, and packaging software.

2. Step 2: Connect with Jenkins pipeline usage

   Jenkins pipelines use these tools to automate software delivery steps efficiently.

3. Final Answer:

   To automate compiling, testing, and packaging code -> Option A

4. Quick Check:

   Build tools automate build tasks = D [OK]

Hint: Build tools automate code build and test steps [OK]

Common Mistakes:

• Confusing build tools with deployment tools
• Thinking build tools write code
• Mixing monitoring tools with build tools

2. Which of the following is the correct Jenkins pipeline syntax to run a Maven build command?

easy

A. sh 'gradle build'

B. bat 'npm install'

C. bat 'mvn deploy'

D. sh 'mvn clean install'

Solution

1. Step 1: Identify the shell command for Maven

   Maven commands run in shell using sh 'mvn ...' in Jenkins on Linux agents.

2. Step 2: Match the correct Maven build command

   mvn clean install compiles and packages the project.

3. Final Answer:

   sh 'mvn clean install' -> Option D

4. Quick Check:

   Maven build command in shell = C [OK]

Hint: Use sh 'mvn clean install' for Maven builds on Linux [OK]

Common Mistakes:

• Using npm or gradle commands for Maven builds
• Using bat instead of sh on Linux agents
• Confusing deploy with build commands

3. Given this Jenkins pipeline snippet, what will be the output if the npm install command fails?

pipeline {
  agent any
  stages {
    stage('Install') {
      steps {
        sh 'npm install'
      }
    }
  }
}

medium

A. Pipeline continues to next stage ignoring failure

B. Pipeline stops and marks build as failed

C. Pipeline retries npm install automatically

D. Pipeline marks build as unstable but continues

Solution

1. Step 1: Understand default Jenkins shell step behavior

   By default, if sh command fails, Jenkins stops the pipeline and marks build as failed.

2. Step 2: Apply this to npm install failure

   If npm install fails, the pipeline will stop immediately and fail.

3. Final Answer:

   Pipeline stops and marks build as failed -> Option B

4. Quick Check:

   Failed shell command stops pipeline = A [OK]

Hint: Failed shell commands stop Jenkins pipeline by default [OK]

Common Mistakes:

• Assuming pipeline continues after failure
• Thinking Jenkins retries commands automatically
• Confusing unstable with failed build status

4. You wrote this Jenkins pipeline step to run Gradle build but it fails with 'command not found':

sh 'gradle build'

What is the most likely cause and fix?

medium

A. Gradle is not installed or not in PATH; install Gradle or set PATH

B. Syntax error in Jenkinsfile; change to bat 'gradle build'

C. Use npm instead of Gradle for Java projects

D. Replace 'build' with 'install' in the command

Solution

1. Step 1: Analyze error 'command not found'

   This error means the system cannot find the gradle command in the PATH.

2. Step 2: Fix by installing Gradle or updating PATH

   Ensure Gradle is installed on the Jenkins agent and its bin directory is in the PATH environment variable.

3. Final Answer:

   Gradle is not installed or not in PATH; install Gradle or set PATH -> Option A

4. Quick Check:

   Command not found means missing install or PATH = A [OK]

Hint: Check PATH and install Gradle if 'command not found' error occurs [OK]

Common Mistakes:

• Using Windows bat syntax on Linux agents
• Confusing npm with Gradle for Java builds
• Changing command without fixing environment

5. You want to create a Jenkins pipeline that runs npm install, then runs tests with npm test, but only if install succeeds. Which pipeline snippet correctly implements this?

hard

A. sh 'npm install; npm test'

B. try {
sh 'npm install'
sh 'npm test'
} catch (e) {
echo 'Install failed'
}

C. sh 'npm install && npm test'

D. sh 'npm test'
sh 'npm install'

Solution

1. Step 1: Understand command chaining with &&

   Using npm install && npm test runs tests only if install succeeds.

2. Step 2: Compare with other options

   sh 'npm install; npm test' runs test regardless because ';' executes the next command irrespective of exit code. try { sh 'npm install' sh 'npm test' } catch (e) { echo 'Install failed' } uses try-catch but Jenkins declarative pipeline syntax does not support this directly. sh 'npm test' sh 'npm install' runs test before install, which is wrong order.

3. Final Answer:

   sh 'npm install && npm test' -> Option C

4. Quick Check:

   Use && to run second command only if first succeeds = B [OK]

Hint: Chain commands with && to run second only if first succeeds [OK]

Common Mistakes:

• Using ';' instead of '&&' to chain commands
• Using try-catch incorrectly in Jenkinsfile
• Running tests before installing dependencies