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.