GitLab CI comparison in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Key difference between GitLab CI and Jenkins pipelines

Which statement best describes a key difference between GitLab CI and Jenkins pipelines?

A Jenkins pipelines cannot be version controlled, but GitLab CI pipelines are stored in a database only.

B GitLab CI requires a separate server installation, while Jenkins is fully cloud-based with no server setup.

C GitLab CI uses a YAML file stored in the repository to define pipelines, while Jenkins uses a separate Jenkinsfile or UI configuration.

D Jenkins pipelines are only triggered manually, whereas GitLab CI pipelines run only on schedule.

💡 Hint

Think about where the pipeline configuration files live and how they are managed.

GitLab CI pipeline definitions are stored as .gitlab-ci.yml files inside the project repository, making them easy to version control. Jenkins pipelines use a Jenkinsfile or UI setup, which may be stored separately.

💻 Command Output

intermediate

Output of Jenkins pipeline stage status

Given this Jenkins pipeline snippet, what will be the output status of the Build stage if the sh command fails?

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        sh 'exit 1'
      }
    }
  }
}

A The Build stage will be marked as FAILED and the pipeline will stop.

B The Build stage will be marked as SUCCESS despite the failure.

C The Build stage will be marked as UNSTABLE and pipeline continues.

D The pipeline will ignore the failure and mark the Build stage as SKIPPED.

💡 Hint

Consider how Jenkins treats shell command exit codes in pipeline steps.

In Jenkins, if a shell command returns a non-zero exit code (like 1), the stage fails and the pipeline stops unless error handling is added.

🔀 Workflow

advanced

Order of GitLab CI pipeline stages execution

What is the correct order of execution for the following GitLab CI stages defined in .gitlab-ci.yml?

A 2,1,3,4

B 1,2,3,4

C 2,3,1,4

D 3,2,1,4

💡 Hint

Remember the typical order of stages in CI/CD pipelines.

Usually, the build stage runs first to create artifacts, then test runs to verify them, followed by deploy and finally cleanup.

❓ Troubleshoot

advanced

Why does Jenkins pipeline fail to trigger on Git push?

A Jenkins pipeline is not triggering automatically when code is pushed to the Git repository. What is the most likely cause?

A The Jenkins agent is offline but triggers still run pipelines.

B The Jenkinsfile syntax is invalid causing the pipeline to skip triggers.

C The Git repository is private and Jenkins cannot clone it manually.

D The Jenkins webhook is not configured or not reachable by the Git server.

💡 Hint

Think about how Jenkins knows when to start a pipeline on Git events.

Jenkins relies on webhooks from the Git server to trigger pipelines automatically. If the webhook is missing or unreachable, no trigger occurs.

✅ Best Practice

expert

Best practice for secret management in GitLab CI vs Jenkins

Which approach is considered best practice for managing secrets securely in GitLab CI compared to Jenkins?

A Use environment variables set manually on build agents without any encryption or masking.

B Use GitLab CI's built-in masked variables and Jenkins credentials plugin to avoid storing secrets in code.

C Commit encrypted secrets files to the repository and decrypt during pipeline execution without external tools.

D Store secrets directly in the pipeline YAML or Jenkinsfile for easy access during builds.

💡 Hint

Consider how each tool supports secret masking and secure storage.

GitLab CI supports masked variables that hide secret values in logs. Jenkins uses a credentials plugin to securely store and inject secrets without exposing them in code.