GitLab CI comparison in Jenkins - Commands & Configuration

Introduction

When teams want to automate software building, testing, and deployment, they use tools called CI/CD systems. GitLab CI and Jenkins are two popular tools that help run these automated steps. Comparing them helps you pick the right tool for your project.

When you want a CI/CD tool tightly integrated with your Git repository and issue tracking.

When you need a highly customizable automation server that supports many plugins.

When you want to run simple pipelines without managing your own servers.

When you want to use a tool that supports many programming languages and environments.

When you want to easily visualize pipeline status and history in your code hosting platform.

Commands

Check the installed Jenkins version to confirm Jenkins is available on your system.

Terminal

jenkins --version

Expected Output

2.387.1

Check the installed GitLab Runner version to confirm GitLab CI runner is available.

Terminal

gitlab-runner --version

Expected Output

Version:      16.0.0

Git revision: 123abc456def

Git branch:   main

Go version:   go1.20.5

Built:        2024-05-15T12:00:00Z

OS/Arch:      linux/amd64

List all Jenkins jobs configured on the Jenkins server to see existing pipelines.

Terminal

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

Expected Output

example-pipeline

build-and-test

deploy-to-prod

List all registered GitLab runners to see which runners are available for GitLab CI jobs.

Terminal

gitlab-runner list

Expected Output

Listing configured runners

Runner ID: 1, Description: my-runner, Active: true, Tags: docker,linux

Key Concept

If you remember nothing else, remember: Jenkins is a standalone automation server with many plugins, while GitLab CI is tightly integrated with GitLab and uses runners to execute jobs.

Common Mistakes

Trying to use Jenkins pipeline syntax directly in GitLab CI configuration.

Jenkins and GitLab CI use different pipeline syntax and configuration files, so they are not interchangeable.

Write separate pipeline configurations: Jenkinsfile for Jenkins and .gitlab-ci.yml for GitLab CI.

Assuming GitLab CI does not require any server setup.

GitLab CI requires GitLab Runner to be installed and registered to execute jobs, which is a separate setup step.

Install and register GitLab Runner properly before running GitLab CI pipelines.

Summary

Jenkins is a flexible automation server with many plugins and requires managing its own server.

GitLab CI is integrated with GitLab and uses runners to execute pipeline jobs.

Both tools automate building, testing, and deploying software but differ in setup and configuration.

Practice

1. Which statement best describes the main difference between Jenkins and GitLab CI?

easy

A. Jenkins cannot automate building and testing.

B. GitLab CI has more plugins than Jenkins.

C. GitLab CI is easier to start with if you already use GitLab for your code.

D. Jenkins is only for deployment, not for testing.

Solution

1. Step 1: Understand GitLab CI's integration

   GitLab CI is built into GitLab, making it simpler to start if your code is hosted there.

2. Step 2: Compare Jenkins capabilities

   Jenkins offers more flexibility and plugins but requires more setup.

3. Final Answer:

   GitLab CI is easier to start with if you already use GitLab for your code. -> Option C

4. Quick Check:

   GitLab CI simpler start = B [OK]

Hint: GitLab CI is simpler if your code is on GitLab [OK]

Common Mistakes:

• Thinking Jenkins cannot automate testing
• Assuming GitLab CI has more plugins
• Believing Jenkins is only for deployment

2. Which of the following is the correct way to define a simple Jenkins pipeline step that echoes 'Hello World'?

easy

A. pipeline { stages { stage('Example') { steps { echo 'Hello World' } } } }

B. pipeline { steps { stage('Example') { echo 'Hello World' } } }

C. pipeline { stage('Example') { steps { print('Hello World') } } }

D. pipeline { stages { step('Example') { echo 'Hello World' } } }

Solution

1. Step 1: Recall Jenkins pipeline syntax

   A Jenkins pipeline requires 'stages' containing 'stage' blocks, each with 'steps'. The echo command is inside steps.

2. Step 2: Identify correct syntax

   pipeline { stages { stage('Example') { steps { echo 'Hello World' } } } } correctly nests stages, stage, steps, and uses echo properly.

3. Final Answer:

   pipeline { stages { stage('Example') { steps { echo 'Hello World' } } } } -> Option A

4. Quick Check:

   Correct Jenkins pipeline syntax = A [OK]

Hint: Remember stages > stage > steps > commands in Jenkins pipeline [OK]

Common Mistakes:

• Placing steps outside stage
• Using print instead of echo
• Misnaming stage as step

3. Given this Jenkins pipeline snippet, what will be the output in the console?

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

medium

A. Build stage skipped, only Testing runs

B. Building...\nTesting...

C. Testing...\nBuilding...

D. Syntax error, pipeline fails

Solution

1. Step 1: Analyze pipeline stages order

   The pipeline runs stages in order: first 'Build', then 'Test'. Each stage echoes its message.

2. Step 2: Determine console output

   The console will show 'Building...' first, then 'Testing...'.

3. Final Answer:

   Building...\nTesting... -> Option B

4. Quick Check:

   Stages run sequentially = C [OK]

Hint: Jenkins stages run in order, echo outputs in sequence [OK]

Common Mistakes:

• Assuming stages run in parallel by default
• Mixing order of outputs
• Thinking pipeline syntax is invalid

4. You have this Jenkins pipeline snippet:

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

What is the problem with this pipeline?

medium

A. The 'Test' stage uses 'step' instead of 'steps', causing a syntax error.

B. The 'Build' stage is missing an agent.

C. The echo command is invalid in Jenkins pipelines.

D. Stages must be defined outside the pipeline block.

Solution

1. Step 1: Check stage syntax

   Each stage must have a 'steps' block, not 'step'. The 'Test' stage incorrectly uses 'step'.

2. Step 2: Understand Jenkins syntax rules

   This causes a syntax error because Jenkins expects 'steps' to group commands.

3. Final Answer:

   The 'Test' stage uses 'step' instead of 'steps', causing a syntax error. -> Option A

4. Quick Check:

   Use 'steps' block in stages = A [OK]

Hint: Stages require 'steps' block, not 'step' [OK]

Common Mistakes:

• Confusing 'step' and 'steps'
• Thinking echo is invalid
• Misplacing stages outside pipeline

5. You want to migrate a simple GitLab CI pipeline to Jenkins. The GitLab CI YAML is:

stages:
  - build
  - test

build_job:
  stage: build
  script:
    - echo "Building..."

test_job:
  stage: test
  script:
    - echo "Testing..."

Which Jenkins pipeline best replicates this behavior?

hard

A. pipeline {
agent any
stages {
stage('build') {
steps {
print('Building...')
}
}
stage('test') {
steps {
print('Testing...')
}
}
}
}

B. pipeline {
agent any
steps {
echo 'Building...'
echo 'Testing...'
}
}

C. pipeline {
agent any
stages {
stage('build') {
step {
echo 'Building...'
}
}
stage('test') {
step {
echo 'Testing...'
}
}
}
}

D. pipeline {
agent any
stages {
stage('build') {
steps {
echo 'Building...'
}
}
stage('test') {
steps {
echo 'Testing...'
}
}
}
}

Solution

1. Step 1: Map GitLab stages to Jenkins stages

   GitLab stages 'build' and 'test' correspond to Jenkins stages named 'build' and 'test'.

2. Step 2: Use correct Jenkins syntax

   Each stage must have a 'steps' block with echo commands to replicate the script commands.

3. Final Answer:

   Jenkins pipeline with stages 'build' and 'test' each having steps with echo commands. -> Option D

4. Quick Check:

   Match GitLab stages with Jenkins stages and steps = D [OK]

Hint: Translate GitLab stages to Jenkins stages with steps and echo [OK]

Common Mistakes:

• Using 'step' instead of 'steps'
• Using print instead of echo
• Putting all commands in one steps block without stages