Blue Ocean interface in Jenkins - Mini Project: Build & Apply

Explore Jenkins Blue Ocean Interface

📖 Scenario: You are a DevOps engineer starting to use Jenkins for continuous integration. Jenkins has a modern interface called Blue Ocean that makes it easier to visualize and manage your pipelines.In this project, you will learn how to set up a simple Jenkins pipeline and explore the Blue Ocean interface to see your pipeline's progress and results.

🎯 Goal: Build a simple Jenkins pipeline script and open it in the Blue Ocean interface to visualize the pipeline stages and results.

📋 What You'll Learn

Create a Jenkins pipeline script with two stages

Add a configuration variable to control a message

Use the variable in the pipeline steps

View the pipeline output in Blue Ocean

💡 Why This Matters

🌍 Real World

Jenkins Blue Ocean interface helps DevOps engineers visualize and manage their continuous integration pipelines easily with a modern UI.

💼 Career

Understanding Jenkins pipelines and Blue Ocean is essential for roles in DevOps, CI/CD engineering, and automation testing.

1

Create a basic Jenkins pipeline script

Create a Jenkins pipeline script called Jenkinsfile with two stages: Build and Test. Each stage should have a simple echo command with the exact messages: Building project... and Testing project... respectively.

Jenkins

// Create a Jenkinsfile with two stages Build and Test
pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                // Your code here
            }
        }
        stage('Test') {
            steps {
                // Your code here
            }
        }
    }
}

Hint

Use the pipeline block with agent any. Define two stage blocks named exactly 'Build' and 'Test'. Inside each, use echo with the exact messages.

2

Add a configuration variable for the message

Add a variable called message at the top of the Jenkinsfile and set it to the string 'Hello from Blue Ocean!'.

Jenkins

def message = 'Hello from Blue Ocean!'

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo 'Building project...'
            }
        }
        stage('Test') {
            steps {
                echo 'Testing project...'
            }
        }
    }
}
// Add the message variable above the pipeline block

Hint

Define def message = 'Hello from Blue Ocean!' before the pipeline block.

3

Use the message variable in the pipeline steps

Modify the Build stage to print the message variable instead of the fixed text. Use echo message exactly.

Jenkins

def message = 'Hello from Blue Ocean!'

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                // Your code here
            }
        }
        stage('Test') {
            steps {
                echo 'Testing project...'
            }
        }
    }
}
// Replace the echo in Build stage with echo message

Hint

Inside the Build stage's steps, replace the fixed echo with echo message.

4

Print the pipeline output in Blue Ocean

Run the pipeline in Jenkins and open the Blue Ocean interface to see the pipeline stages and output. Then write echo 'Pipeline completed successfully' as the last step in the Test stage to confirm completion.

Jenkins

def message = 'Hello from Blue Ocean!'

pipeline {
    agent any
    stages {
        stage('Build') {
            steps {
                echo message
            }
        }
        stage('Test') {
            steps {
                echo 'Testing project...'
                // Your code here
            }
        }
    }
}
// Add echo 'Pipeline completed successfully' as last step in Test stage

Hint

In the Test stage's steps, add echo 'Pipeline completed successfully' after the existing echo.

Run the pipeline and open Blue Ocean to see the stages and messages.

Practice

1. What is the main purpose of the Jenkins Blue Ocean interface?

easy

A. To replace Jenkins core with a new backend system

B. To write Jenkins pipeline scripts automatically

C. To run Jenkins jobs faster using cloud resources

D. To provide a modern, visual way to view and manage pipelines

Solution

1. Step 1: Understand Blue Ocean's role

   Blue Ocean is designed to improve the user experience by showing pipelines visually.

2. Step 2: Compare options

   Options A, C, and D describe backend or automation features, not the interface purpose.

3. Final Answer:

   To provide a modern, visual way to view and manage pipelines -> Option D

4. Quick Check:

   Blue Ocean = Visual pipeline interface [OK]

Hint: Blue Ocean = Visual pipeline dashboard in Jenkins [OK]

Common Mistakes:

• Thinking Blue Ocean changes Jenkins backend
• Confusing Blue Ocean with pipeline automation tools
• Assuming Blue Ocean speeds up job execution

2. Which of the following is the correct way to open the Blue Ocean interface in Jenkins?

easy

A. Click on 'New Item' and select 'Blue Ocean Pipeline'

B. Click on 'Open Blue Ocean' button in the Jenkins dashboard

C. Run the command 'jenkins blueocean start' in terminal

D. Navigate to 'Manage Jenkins' and enable Blue Ocean plugin

Solution

1. Step 1: Identify how to access Blue Ocean

   Blue Ocean is accessed via a button labeled 'Open Blue Ocean' on the Jenkins dashboard.

2. Step 2: Evaluate other options

   Click on 'New Item' and select 'Blue Ocean Pipeline' is for creating new items, not opening Blue Ocean. Run the command 'jenkins blueocean start' in terminal is not a valid command. Navigate to 'Manage Jenkins' and enable Blue Ocean plugin is about plugin management, not opening the interface.

3. Final Answer:

   Click on 'Open Blue Ocean' button in the Jenkins dashboard -> Option B

4. Quick Check:

   Blue Ocean button opens interface [OK]

Hint: Look for 'Open Blue Ocean' button on Jenkins main page [OK]

Common Mistakes:

• Trying to open Blue Ocean via terminal commands
• Confusing plugin installation with interface access
• Selecting 'New Item' instead of opening Blue Ocean

3. In Blue Ocean, what does a green checkmark on a pipeline stage indicate?

medium

A. The stage has completed successfully

B. The stage is currently running

C. The stage has failed

D. The stage is skipped

Solution

1. Step 1: Understand Blue Ocean stage icons

   A green checkmark means success, showing the stage finished without errors.

2. Step 2: Match icons to meanings

   Running stages show a spinner, failures show red crosses, skipped stages show grey icons.

3. Final Answer:

   The stage has completed successfully -> Option A

4. Quick Check:

   Green checkmark = success [OK]

Hint: Green checkmark means success in Blue Ocean stages [OK]

Common Mistakes:

• Confusing green checkmark with running status
• Thinking green means skipped or failed
• Ignoring icon color meanings

4. You opened Blue Ocean but see no pipelines listed. What is the most likely cause?

medium

A. No pipelines have been created or imported yet

B. Blue Ocean plugin is not installed

C. Jenkins server is offline

D. You are not logged in to Jenkins

Solution

1. Step 1: Check pipeline existence

   If no pipelines show, usually none exist or were imported yet.

2. Step 2: Rule out other causes

   If Blue Ocean plugin was missing, interface wouldn't open. Server offline or login issues prevent access entirely.

3. Final Answer:

   No pipelines have been created or imported yet -> Option A

4. Quick Check:

   No pipelines = none created [OK]

Hint: No pipelines listed means none created yet [OK]

Common Mistakes:

• Assuming plugin missing if interface opens
• Blaming server offline without checking connection
• Ignoring login status when interface is accessible

5. You want to create a new pipeline using Blue Ocean that automatically detects your GitHub repository. Which step should you take first?

hard

A. Create a freestyle project and add GitHub URL

B. Manually write a Jenkinsfile in the Jenkins classic UI

C. Click 'New Pipeline' in Blue Ocean and connect your GitHub account

D. Install the GitHub plugin from Jenkins plugin manager

Solution

1. Step 1: Use Blue Ocean's pipeline creation

   Blue Ocean lets you create pipelines by connecting your GitHub account to auto-detect repos.

2. Step 2: Understand alternatives

   Writing Jenkinsfile manually or freestyle projects are older methods. Plugin installation is prerequisite but usually done beforehand.

3. Final Answer:

   Click 'New Pipeline' in Blue Ocean and connect your GitHub account -> Option C

4. Quick Check:

   New Pipeline + GitHub connect = auto detect [OK]

Hint: Start new pipeline in Blue Ocean and link GitHub [OK]

Common Mistakes:

• Skipping Blue Ocean pipeline creation wizard
• Trying freestyle projects for pipeline automation
• Forgetting to connect GitHub account in Blue Ocean