Hybrid CI/CD approaches in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Hybrid CI/CD Pipelines

In a hybrid CI/CD approach, which of the following best describes the main advantage?

A It combines on-premises and cloud resources to optimize build and deployment speed.

B It uses only cloud resources to reduce costs and complexity.

C It requires manual intervention at every stage to ensure quality.

D It eliminates the need for version control systems.

💡 Hint

Think about how hybrid approaches balance different environments.

Hybrid CI/CD pipelines leverage both on-premises and cloud environments to improve speed and flexibility, unlike purely cloud or manual approaches.

💻 Command Output

intermediate

Jenkins Pipeline Output with Hybrid Agents

Given this Jenkinsfile snippet using hybrid agents:

pipeline {
  agent none
  stages {
    stage('Build') {
      agent { label 'on-prem-agent' }
      steps {
        echo 'Building on on-premises agent'
      }
    }
    stage('Deploy') {
      agent { label 'cloud-agent' }
      steps {
        echo 'Deploying on cloud agent'
      }
    }
  }
}

What will be the console output when this pipeline runs?

Jenkins

pipeline {
  agent none
  stages {
    stage('Build') {
      agent { label 'on-prem-agent' }
      steps {
        echo 'Building on on-premises agent'
      }
    }
    stage('Deploy') {
      agent { label 'cloud-agent' }
      steps {
        echo 'Deploying on cloud agent'
      }
    }
  }
}

A Error: Agent label 'on-prem-agent' not found

B [Pipeline] stage\n[Pipeline] { (Build)\nDeploying on cloud agent\n[Pipeline] }\n[Pipeline] stage\n[Pipeline] { (Deploy)\nBuilding on on-premises agent\n[Pipeline] }

C [Pipeline] stage\n[Pipeline] { (Build)\nBuilding on on-premises agent\n[Pipeline] }\n[Pipeline] stage\n[Pipeline] { (Deploy)\nDeploying on cloud agent\n[Pipeline] }

D Error: Agent label 'cloud-agent' not found

💡 Hint

Each stage uses its own agent label to run steps.

The pipeline runs the 'Build' stage on the on-premises agent and the 'Deploy' stage on the cloud agent, printing messages accordingly.

❓ Configuration

advanced

Configuring Jenkins for Hybrid CI/CD

Which Jenkins configuration snippet correctly sets up a hybrid pipeline that uses a Docker container on a cloud agent for testing and an on-premises agent for building?

A

pipeline {
  agent none
  stages {
    stage('Build') {
      agent { docker { image 'python:3.12' label 'on-prem-agent' } }
      steps {
        sh 'make build'
      }
    }
    stage('Test') {
      agent { label 'cloud-agent' }
      steps {
        sh 'pytest'
      }
    }
  }
}

B

pipeline {
  agent none
  stages {
    stage('Build') {
      agent { label 'on-prem-agent' }
      steps {
        sh 'make build'
      }
    }
    stage('Test') {
      agent {
        docker {
          image 'python:3.12'
          label 'cloud-agent'
        }
      }
      steps {
        sh 'pytest'
      }
    }
  }
}

C

pipeline {
  agent { label 'cloud-agent' }
  stages {
    stage('Build') {
      steps {
        sh 'make build'
      }
    }
    stage('Test') {
      agent { docker { image 'python:3.12' } }
      steps {
        sh 'pytest'
      }
    }
  }
}

D

pipeline {
  agent {
    docker {
      image 'python:3.12'
      label 'on-prem-agent'
    }
  }
  stages {
    stage('Build') {
      steps {
        sh 'make build'
      }
    }
    stage('Test') {
      agent { label 'cloud-agent' }
      steps {
        sh 'pytest'
      }
    }
  }
}

💡 Hint

Remember that Docker agent inside a stage requires both image and label separately.

Option B correctly assigns the on-premises agent for build and uses a Docker container on the cloud agent for testing. Other options misuse agent blocks or combine labels incorrectly.

❓ Troubleshoot

advanced

Troubleshooting Hybrid Pipeline Agent Errors

A Jenkins hybrid pipeline fails with the error: java.lang.IllegalArgumentException: No agent found with label 'cloud-agent'. What is the most likely cause?

A The label 'cloud-agent' is not assigned to any active Jenkins agent node.

B The Jenkins master node is offline, causing all agents to be unreachable.

C The pipeline syntax is incorrect and missing the 'agent' block entirely.

D The Docker image specified for the cloud agent is invalid or missing.

💡 Hint

Check the agent labels configured in Jenkins nodes.

The error indicates Jenkins cannot find any agent with the label 'cloud-agent'. This usually means no node has that label assigned or the node is offline.

🔀 Workflow

expert

Hybrid CI/CD Workflow Optimization

You have a hybrid CI/CD setup where builds run on-premises and deployments run in the cloud. Which workflow change will best reduce deployment downtime during updates?

A Use manual approval steps before deployment to ensure no errors occur.

B Move all builds and deployments to the on-premises environment to reduce network latency.

C Run builds and deployments simultaneously on both on-premises and cloud agents.

D Implement blue-green deployment in the cloud environment while keeping builds on-premises.

💡 Hint

Think about deployment strategies that minimize downtime.

Blue-green deployment allows switching traffic between two identical environments, reducing downtime during updates. Keeping builds on-premises maintains hybrid benefits.