Jenkins to GitHub Actions path - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a GitHub Actions workflow trigger for push events.

Jenkins

on: [1]

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

Apush

Bpull_request

Cschedule

Dworkflow_dispatch

Attempts:

3 left

💡 Hint

Common Mistakes

Using pull_request instead of push for push events.

The on key defines the event that triggers the workflow. For push events, use push.

2fill in blank

medium

Complete the code to specify the job runner environment in GitHub Actions.

Jenkins

jobs:
  build:
    runs-on: [1]

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

Amacos-latest

Bwindows-latest

Cubuntu-latest

Dself-hosted

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing windows-latest when Linux is expected.

The runs-on key sets the virtual machine environment. ubuntu-latest is a common choice for Linux runners.

3fill in blank

hard

Fix the error in the GitHub Actions step to run a shell command.

Jenkins

steps:
  - name: Run tests
    run: [1]

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

Aexecute npm test

Bnpm test

Cnpm-test

Drun npm test

Attempts:

3 left

💡 Hint

Common Mistakes

Adding extra words like 'run' or 'execute' before the command.

The run key expects a shell command. npm test is the correct command to run tests.

4fill in blank

hard

Fill both blanks to define a step that checks out the repository code in GitHub Actions.

Jenkins

steps:
  - name: Checkout code
    uses: [1]
    with:
      [2]: 'v3'

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

Aactions/checkout@v3

Bactions/setup-node@v3

Cref

Dnode-version

Attempts:

3 left

💡 Hint

Common Mistakes

Using setup-node action instead of checkout.

Using 'node-version' instead of 'ref'.

The actions/checkout@v3 action checks out the code. The ref input specifies the branch or tag version.

5fill in blank

hard

Fill all three blanks to define a job that installs dependencies, runs tests, and builds the project.

Jenkins

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Install dependencies
        run: [1]
      - name: Run tests
        run: [2]
      - name: Build project
        run: [3]

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

Anpm install

Bnpm test

Cnpm run build

Dnpm start

Attempts:

3 left

💡 Hint

Common Mistakes

Running tests before installing dependencies.

Using 'npm start' instead of 'npm run build' for building.

First, install dependencies with npm install. Then run tests with npm test. Finally, build the project with npm run build.

Practice

1. What is the main difference between Jenkins and GitHub Actions in terms of where the automation configuration is stored?

easy

A. Both Jenkins and GitHub Actions store workflows only on external servers.

B. GitHub Actions stores workflow files inside the repository, Jenkins uses an external server.

C. Jenkins stores workflows inside the repository, GitHub Actions uses an external server.

D. Both Jenkins and GitHub Actions store workflows only inside the repository.

Solution

1. Step 1: Understand Jenkins workflow storage

   Jenkins typically stores job configurations on its own server, separate from the code repository.

2. Step 2: Understand GitHub Actions workflow storage

   GitHub Actions stores workflow YAML files directly inside the code repository under the .github/workflows directory.

3. Final Answer:

   GitHub Actions stores workflow files inside the repository, Jenkins uses an external server. -> Option B

4. Quick Check:

   Workflow location = repository for GitHub Actions [OK]

Hint: Remember: GitHub Actions config lives with your code [OK]

Common Mistakes:

• Thinking Jenkins stores configs in the repo
• Assuming GitHub Actions uses external servers only
• Confusing storage locations for both tools

2. Which of the following is the correct syntax to trigger a GitHub Actions workflow on a push to the main branch?

easy

A. on: push: branches: [main]

B. trigger: push main

C. event: push branch main

D. when: push to main

Solution

1. Step 1: Recall GitHub Actions trigger syntax

   The correct YAML syntax uses 'on:' followed by the event type and branches list.

2. Step 2: Match syntax to options

   on: push: branches: [main] matches the correct YAML format: 'on: push: branches: [main]'. Others are invalid YAML or incorrect keywords.

3. Final Answer:

   on: push: branches: [main] -> Option A

4. Quick Check:

   Trigger syntax = 'on:' keyword [OK]

Hint: GitHub Actions triggers start with 'on:' in YAML [OK]

Common Mistakes:

• Using 'trigger' instead of 'on' keyword
• Incorrect YAML indentation or keywords
• Confusing event names and branch filters

3. Given this GitHub Actions workflow snippet, what will happen when a pull request is opened?

on:
  pull_request:
    branches:
      - main
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v3
      - name: Run tests
        run: echo "Tests running..."

medium

A. The workflow runs only when a pull request targets the main branch.

B. The workflow runs on any pull request regardless of target branch.

C. The workflow runs only on push events, not pull requests.

D. The workflow will fail due to syntax errors.

Solution

1. Step 1: Analyze the trigger section

   The workflow triggers on pull_request events targeting the 'main' branch only.

2. Step 2: Understand job execution

   When a pull request is opened against 'main', the job runs the steps: checkout and echo test message.

3. Final Answer:

   The workflow runs only when a pull request targets the main branch. -> Option A

4. Quick Check:

   Trigger filters = pull_request on main branch [OK]

Hint: Check 'on:' and branch filters to predict workflow triggers [OK]

Common Mistakes:

• Assuming it runs on all pull requests
• Confusing push and pull_request triggers
• Thinking syntax is invalid when it is correct

4. You migrated a Jenkins pipeline to GitHub Actions but the workflow does not run on push events. Which is the most likely cause?

medium

A. The workflow file is named with a .json extension instead of .yml.

B. The Jenkinsfile syntax was copied directly into the GitHub Actions YAML.

C. The repository is private and GitHub Actions only works on public repos.

D. The workflow YAML file is not placed under the .github/workflows directory.

Solution

1. Step 1: Check workflow file location

   GitHub Actions requires workflow files to be inside the .github/workflows folder to detect and run them.

2. Step 2: Evaluate other options

   Copying Jenkinsfile syntax won't run but does not prevent detection; GitHub Actions works on private repos; file extension must be .yml or .yaml, but location is primary cause.

3. Final Answer:

   The workflow YAML file is not placed under the .github/workflows directory. -> Option D

4. Quick Check:

   Workflow location = .github/workflows folder [OK]

Hint: Put workflow files in .github/workflows folder [OK]

Common Mistakes:

• Ignoring file location importance
• Assuming Jenkinsfile syntax works in GitHub Actions
• Thinking GitHub Actions only runs on public repos

5. You want to convert a Jenkins pipeline that runs tests on multiple operating systems into a GitHub Actions workflow. Which approach correctly replicates this behavior?

hard

A. Create separate workflows for each OS and trigger them manually.

B. Use a single job with a shell script that switches OS environments inside the runner.

C. Use a matrix strategy in GitHub Actions to run jobs on ubuntu-latest, windows-latest, and macos-latest runners.

D. GitHub Actions does not support multiple OS testing; use Jenkins instead.

Solution

1. Step 1: Understand Jenkins multi-OS testing

   Jenkins pipelines can run parallel jobs on different OS agents to test across environments.

2. Step 2: Use GitHub Actions matrix strategy

   GitHub Actions supports a matrix strategy to run the same job on multiple OS runners like ubuntu-latest, windows-latest, and macos-latest automatically.

3. Final Answer:

   Use a matrix strategy in GitHub Actions to run jobs on ubuntu-latest, windows-latest, and macos-latest runners. -> Option C

4. Quick Check:

   Matrix strategy = multi-OS testing [OK]

Hint: Use matrix to test multiple OS in one workflow [OK]

Common Mistakes:

• Trying to switch OS inside one runner
• Creating many manual workflows instead of matrix
• Believing GitHub Actions lacks multi-OS support