CI/CD tools landscape in Jenkins - Commands & Configuration

Introduction

CI/CD tools help automate the process of building, testing, and delivering software. They solve the problem of manual, error-prone deployments by making software delivery faster and more reliable.

When you want to automatically test your code every time you save changes.

When you need to deploy your app to a server without doing it by hand.

When multiple developers work on the same project and need a shared build process.

When you want to catch bugs early by running tests automatically.

When you want to deliver updates to users quickly and safely.

Commands

This command starts the Jenkins server on your machine so you can access the web interface to create and manage your CI/CD pipelines.

Terminal

java -jar jenkins.war

Expected Output

Running from: /home/user/jenkins.war

2024-06-01 12:00:00.000+0000 [id=1]    INFO    org.eclipse.jetty.server.Server#doStart: Started @12345ms

Jenkins is fully up and running

This command checks if Jenkins is running by requesting its API endpoint. It returns JSON data about the Jenkins server status.

Terminal

curl http://localhost:8080/api/json

Expected Output

{"assignedLabels":[{}],"mode":"NORMAL","nodeDescription":"the master Jenkins node","numExecutors":2,"description":null,"jobs":[],"overallLoad":{},"primaryView":{"name":"All"},"quietingDown":false,"slaveAgentPort":50000,"unlabeledLoad":{},"useCrumbs":true,"useSecurity":true,"views":[{"name":"All"}]}

This command lists all jobs configured in Jenkins using the Jenkins CLI tool. It helps verify what pipelines are available.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080/ list-jobs

Expected Output

No output (command runs silently)

→

-s - Specifies the Jenkins server URL

Key Concept

If you remember nothing else from this pattern, remember: CI/CD tools automate software building, testing, and deployment to save time and reduce errors.

Common Mistakes

Trying to start Jenkins without Java installed

Jenkins runs on Java, so without Java the server won't start and you get errors.

Install Java (version 11 or newer) before running Jenkins.

Not checking if Jenkins is running before using CLI commands

CLI commands fail if the Jenkins server is not running or reachable.

Always verify Jenkins is running by accessing the web UI or using curl before running CLI commands.

Summary

Start Jenkins server with 'java -jar jenkins.war' to access the web interface.

Check Jenkins status using its API with curl to ensure it is running.

Use Jenkins CLI to list and manage jobs for automation pipelines.

Practice

1. What is the main purpose of CI/CD tools like Jenkins in software development?

easy

A. To design user interfaces

B. To write code manually

C. To automate building, testing, and deploying software

D. To manage hardware resources

Solution

1. Step 1: Understand CI/CD tools role

   CI/CD tools automate repetitive tasks in software development like building, testing, and deploying.

2. Step 2: Compare options

   Options B, C, and D describe unrelated tasks. Only To automate building, testing, and deploying software matches the automation purpose.

3. Final Answer:

   To automate building, testing, and deploying software -> Option C

4. Quick Check:

   CI/CD tools automate software delivery = A [OK]

Hint: CI/CD tools automate software delivery steps [OK]

Common Mistakes:

• Confusing CI/CD tools with coding or design tools
• Thinking CI/CD tools manage hardware
• Assuming CI/CD tools replace developers

2. Which of the following is the correct way to define a stage in a Jenkins pipeline?

easy

A. stage('Build') { steps { echo 'Building...' } }

B. step('Build') { echo 'Building...' }

C. stage: Build { echo 'Building...' }

D. buildStage { echo 'Building...' }

Solution

1. Step 1: Recall Jenkins pipeline syntax

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

2. Step 2: Check options for correct syntax

   Only stage('Build') { steps { echo 'Building...' } } matches the correct syntax with stage and steps blocks.

3. Final Answer:

   <code>stage('Build') { steps { echo 'Building...' } }</code> -> Option A

4. Quick Check:

   Correct Jenkins stage syntax = C [OK]

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

Common Mistakes:

• Using 'step' instead of 'stage'
• Missing the steps block inside stage
• Incorrect block syntax with colons or missing braces

3. Given this Jenkins pipeline snippet, what will be printed during the 'Test' stage?

pipeline {
  agent any
  stages {
    stage('Build') {
      steps { echo 'Building...' }
    }
    stage('Test') {
      steps { echo 'Testing...' }
    }
  }
}

medium

A. Testing... Building...

B. Testing...

C. Building...

D. Building... Testing...

Solution

1. Step 1: Understand pipeline stage order

   The pipeline runs stages in order: 'Build' then 'Test'.

2. Step 2: Identify echo outputs

   'Build' stage prints 'Building...', 'Test' stage prints 'Testing...'. Both run sequentially.

3. Final Answer:

   Building... Testing... -> Option D

4. Quick Check:

   Stages run in order, print messages in sequence = B [OK]

Hint: Stages run sequentially, outputs print in order [OK]

Common Mistakes:

• Assuming stages run in parallel by default
• Mixing output order
• Ignoring all stages run unless skipped

4. Identify the error in this Jenkins pipeline snippet:

pipeline {
  agent any
  stages {
    stage('Deploy') {
      step { echo 'Deploying...' }
    }
  }
}

medium

A. The keyword should be 'steps' not 'step'

B. Missing agent declaration

C. Stage name must be lowercase

D. Echo command is invalid

Solution

1. Step 1: Check pipeline syntax for stages

   Inside a stage, the correct block is steps (plural), not step.

2. Step 2: Verify other parts

   Agent is declared, stage name case is allowed, echo is valid. Only 'step' is wrong.

3. Final Answer:

   The keyword should be 'steps' not 'step' -> Option A

4. Quick Check:

   Use 'steps' block inside stage = A [OK]

Hint: Inside stage use 'steps' plural block [OK]

Common Mistakes:

• Using 'step' instead of 'steps'
• Thinking stage names must be lowercase
• Assuming echo is not allowed

5. You want to create a Jenkins pipeline that builds, tests, and deploys only if tests pass. Which approach best fits this CI/CD workflow?

hard

A. Skip Test stage and deploy immediately after Build

B. Define sequential stages: Build, Test, Deploy; Deploy runs only if Test succeeds

C. Deploy first, then Build and Test in any order

D. Run Build and Deploy stages in parallel, then Test last

Solution

1. Step 1: Understand CI/CD workflow logic

   Tests must pass before deploying to avoid broken releases.

2. Step 2: Choose pipeline structure

   Sequential stages Build -> Test -> Deploy ensure deploy runs only if tests succeed.

3. Step 3: Evaluate other options

   Parallel or skipping tests risks deploying broken code; deploying first is illogical.

4. Final Answer:

   Define sequential stages: Build, Test, Deploy; Deploy runs only if Test succeeds -> Option B

5. Quick Check:

   Sequential stages with test gate = D [OK]

Hint: Deploy only after successful tests in sequence [OK]

Common Mistakes:

• Running deploy before tests
• Skipping tests to save time
• Running build and deploy in parallel