GitHub Actions comparison in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Key difference between GitHub Actions and Jenkins pipelines

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

A GitHub Actions requires manual installation on local servers, Jenkins runs only in the cloud.

B Jenkins only supports Windows agents, whereas GitHub Actions supports Linux and macOS agents.

C GitHub Actions is tightly integrated with GitHub repositories, while Jenkins is a standalone automation server that requires separate setup.

D Jenkins pipelines cannot be defined as code, but GitHub Actions workflows can.

💡 Hint

Think about where each tool runs and how they connect to your code.

GitHub Actions is built into GitHub and works directly with repositories, while Jenkins is a separate tool you install and manage yourself.

💻 Command Output

intermediate

Output of Jenkins pipeline step vs GitHub Actions step

Given a Jenkins pipeline step and a GitHub Actions step that both print 'Hello World', what is the difference in their console output format?

Jenkins

Jenkins pipeline step:
steps {
  echo 'Hello World'
}

GitHub Actions step:
- name: Print greeting
  run: echo 'Hello World'

A Jenkins output includes step name and timestamps; GitHub Actions output shows step name and command run.

B Both outputs are identical with only 'Hello World' printed.

C GitHub Actions output includes timestamps; Jenkins output does not.

D Jenkins output is JSON formatted; GitHub Actions output is plain text.

💡 Hint

Consider how each tool formats logs for readability.

Jenkins logs show step names and timestamps by default, while GitHub Actions logs show step names and the commands executed.

🔀 Workflow

advanced

Choosing the right runner for GitHub Actions

You want to run a GitHub Actions workflow that builds a Java project and deploys it to a Linux server. Which runner choice is best and why?

A Use GitHub-hosted Ubuntu runner for build and a self-hosted Linux runner for deployment.

B Use only GitHub-hosted Windows runners for both build and deployment.

C Use self-hosted Windows runner for build and GitHub-hosted macOS runner for deployment.

D Use only GitHub-hosted macOS runners for both build and deployment.

💡 Hint

Think about compatibility and control over deployment environment.

GitHub-hosted Ubuntu runners are good for building Java projects, and a self-hosted Linux runner gives control for deployment to your Linux server.

❓ Troubleshoot

advanced

Troubleshooting GitHub Actions workflow failure due to permissions

A GitHub Actions workflow fails with a permissions error when trying to push code back to the repository. What is the most likely cause?

A The repository is private and GitHub Actions cannot run on private repos.

B The workflow is using the default GITHUB_TOKEN which lacks write permissions to push changes.

C The workflow YAML syntax is invalid causing permission errors.

D GitHub Actions runners do not support git push commands.

💡 Hint

Consider the token permissions used by GitHub Actions by default.

The default GITHUB_TOKEN has write permissions by default; to push code, you must explicitly grant write permissions or use a personal access token.

✅ Best Practice

expert

Best practice for secret management in GitHub Actions vs Jenkins

Which approach is considered best practice for managing secrets in GitHub Actions compared to Jenkins?

A Use third-party secret managers only for Jenkins; GitHub Actions does not support secret management.

B Store secrets in plain text files checked into the repository for both tools.

C Use environment variables hardcoded in workflow files for GitHub Actions and Jenkinsfiles.

D Use GitHub Secrets encrypted storage for GitHub Actions and Jenkins Credentials Plugin for Jenkins.

💡 Hint

Think about built-in secret storage features each tool offers.

GitHub Actions uses encrypted secrets stored in the repository settings, while Jenkins uses the Credentials Plugin to securely store secrets.

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