GitHub Actions comparison in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Jenkins pipeline stage.

Jenkins

stage('[1]') {
    steps {
        echo 'Building the project'
    }
}

Drag options to blanks, or click blank then click option'

ACleanup

BTest

CDeploy

DBuild

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Test' or 'Deploy' as the first stage name.

The stage name should be 'Build' to indicate the build step in the pipeline.

2fill in blank

medium

Complete the code to trigger a Jenkins pipeline on a GitHub push event.

Jenkins

pipeline {
    agent any
    triggers {
        [1]()
    }
    stages {
        stage('Build') {
            steps {
                echo 'Building...'
            }
        }
    }
}

Drag options to blanks, or click blank then click option'

AgithubPush

Bcron

CpollSCM

DgithubPushTrigger

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'cron' which is a time-based trigger.

The 'pollSCM' trigger is commonly used to poll the source control for changes, including GitHub push events.

3fill in blank

hard

Fix the error in the Jenkinsfile snippet to correctly checkout code from GitHub.

Jenkins

pipeline {
    agent any
    stages {
        stage('Checkout') {
            steps {
                [1] scm
            }
        }
    }
}

Drag options to blanks, or click blank then click option'

Acheckout

Bclone

CgitCheckout

Dpull

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'clone' or 'pull' which are git commands but not Jenkins steps.

The correct Jenkins pipeline step to checkout code is 'checkout scm'.

4fill in blank

hard

Fill both blanks to define environment variables and use them in a Jenkins pipeline.

Jenkins

pipeline {
    agent any
    environment {
        APP_NAME = '[1]'
        APP_ENV = '[2]'
    }
    stages {
        stage('Print Env') {
            steps {
                echo "App: $APP_NAME, Environment: $APP_ENV"
            }
        }
    }
}

Drag options to blanks, or click blank then click option'

AMyApp

BProduction

CDevelopment

DTest

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing environment names or using invalid variable names.

Setting APP_NAME to 'MyApp' and APP_ENV to 'Production' shows how to define and use environment variables.

5fill in blank

hard

Fill all three blanks to create a Jenkins pipeline stage that runs a shell command with parameters.

Jenkins

pipeline {
    agent any
    stages {
        stage('[1]') {
            steps {
                sh '[2] [3]'
            }
        }
    }
}

Drag options to blanks, or click blank then click option'

ATest

Bnpm test

C--verbose

DBuild

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong stage names or incomplete shell commands.

The stage is named 'Test', running 'npm test --verbose' as the shell command.

Practice

1. Which statement best describes a key difference between Jenkins and GitHub Actions?

easy

A. GitHub Actions requires more plugins than Jenkins to run pipelines.

B. Jenkins offers more customization and plugins, while GitHub Actions is easier to set up inside GitHub.

C. Jenkins can only be used with GitHub repositories.

D. GitHub Actions cannot automate workflows.

Solution

1. Step 1: Understand Jenkins capabilities

   Jenkins is known for its extensive customization and plugin support for complex pipelines.

2. Step 2: Understand GitHub Actions setup

   GitHub Actions is integrated into GitHub and is easier to set up for repositories hosted there.

3. Final Answer:

   Jenkins offers more customization and plugins, while GitHub Actions is easier to set up inside GitHub. -> Option B

4. Quick Check:

   Customization vs ease of setup = A [OK]

Hint: Remember Jenkins = plugins, GitHub Actions = quick GitHub setup [OK]

Common Mistakes:

• Thinking GitHub Actions needs more plugins than Jenkins
• Believing Jenkins only works with GitHub
• Assuming GitHub Actions cannot automate workflows

2. Which of the following is the correct way to trigger a GitHub Actions workflow on a push event?

easy

A. on: push

B. trigger: push

C. event: push

D. start: push

Solution

1. Step 1: Recall GitHub Actions syntax

   The correct keyword to specify events in GitHub Actions YAML is on.

2. Step 2: Identify correct event format

   To trigger on push, use on: push. Other options are invalid syntax.

3. Final Answer:

   on: push -> Option A

4. Quick Check:

   Event trigger keyword = on [OK]

Hint: GitHub Actions uses 'on' to specify events [OK]

Common Mistakes:

• Using 'trigger' or 'event' instead of 'on'
• Writing 'start' which is not valid
• Confusing Jenkins syntax with GitHub Actions

3. Given this GitHub Actions snippet, what will happen when a push occurs?

on: push
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - run: echo "Build started"

medium

A. It causes a syntax error and fails.

B. It triggers a Jenkins job instead of GitHub Actions.

C. It prints 'Build started' in the workflow logs.

D. It does nothing because no build steps are defined.

Solution

1. Step 1: Analyze the workflow trigger

   The workflow triggers on push events as specified by on: push.

2. Step 2: Check the job steps

   The job runs on Ubuntu and executes a step that echoes 'Build started'. This will appear in logs.

3. Final Answer:

   It prints 'Build started' in the workflow logs. -> Option C

4. Quick Check:

   Push triggers echo step = prints message [OK]

Hint: Look for 'run' steps to see what commands execute [OK]

Common Mistakes:

• Confusing Jenkins jobs with GitHub Actions jobs
• Assuming missing build steps means no action
• Thinking syntax error without checking YAML carefully

4. You wrote this GitHub Actions workflow but it never triggers on push:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - run: echo "Build started"

What is the likely problem?

medium

A. GitHub Actions does not support echo commands.

B. The runs-on value is incorrect.

C. The steps section is empty.

D. Missing the on: push event trigger.

Solution

1. Step 1: Check for event triggers

   The workflow lacks the on: push line, so it has no trigger defined.

2. Step 2: Understand trigger necessity

   Without an event trigger, GitHub Actions will not run the workflow automatically.

3. Final Answer:

   Missing the on: push event trigger. -> Option D

4. Quick Check:

   Event trigger missing = no workflow run [OK]

Hint: Always include 'on' to trigger workflows [OK]

Common Mistakes:

• Assuming runs-on value causes trigger failure
• Thinking empty steps cause no trigger
• Believing echo commands are unsupported

5. You want to migrate a Jenkins pipeline to GitHub Actions but your Jenkins pipeline uses many plugins for deployment. What is the best approach?

hard

A. Check if GitHub Actions has equivalent actions or write custom scripts to replace plugins.

B. Directly copy Jenkinsfile to GitHub Actions workflow YAML.

C. Use Jenkins plugins inside GitHub Actions without changes.

D. Stop using deployment in GitHub Actions because plugins are not supported.

Solution

1. Step 1: Understand plugin differences

   Jenkins plugins do not work directly in GitHub Actions; equivalents or scripts are needed.

2. Step 2: Plan migration strategy

   Look for GitHub Actions marketplace actions or write scripts to replicate Jenkins plugin functionality.

3. Final Answer:

   Check if GitHub Actions has equivalent actions or write custom scripts to replace plugins. -> Option A

4. Quick Check:

   Replace Jenkins plugins with GitHub Actions equivalents [OK]

Hint: Find GitHub Actions marketplace actions to replace Jenkins plugins [OK]

Common Mistakes:

• Trying to use Jenkins plugins directly in GitHub Actions
• Copying Jenkinsfile YAML as-is
• Giving up on deployment in GitHub Actions