CI pipeline setup in Remix - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the branch to trigger the CI pipeline.

Remix

on:
  push:
    branches:
      - [1]

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

Atest

Bbuild

Cmain

Ddeploy

Attempts:

3 left

💡 Hint

Common Mistakes

Using a branch name that does not exist in the repository.

Using a feature branch instead of the main branch.

The main branch is commonly used as the primary branch to trigger CI pipelines.

2fill in blank

medium

Complete the code to run the job on the latest Ubuntu runner.

Remix

jobs:
  build:
    runs-on: [1]

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

Awindows-latest

Bubuntu-latest

Cdebian-latest

Dmacos-latest

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a Windows or macOS runner when Linux is preferred.

Using an unsupported runner label.

The ubuntu-latest runner is commonly used for Linux-based CI jobs.

3fill in blank

hard

Fix the error in the step to install dependencies using npm.

Remix

steps:
  - name: Install dependencies
    run: npm [1]

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

Ainstall

Bbuild

Cstart

Dtest

Attempts:

3 left

💡 Hint

Common Mistakes

Using npm build which is not a valid npm command.

Using npm start which runs the app instead of installing.

The npm install command installs all dependencies listed in package.json.

4fill in blank

hard

Fill both blanks to run tests and then build the Remix app.

Remix

steps:
  - name: Run tests
    run: npm [1]
  - name: Build app
    run: npm [2]

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

Atest

Bbuild

Cinstall

Dstart

Attempts:

3 left

💡 Hint

Common Mistakes

Running npm start instead of npm run build for building.

Skipping tests before building.

First, tests are run with npm test. Then the app is built with npm run build.

5fill in blank

hard

Fill all three blanks to define a job that checks out code, installs dependencies, and runs tests.

Remix

jobs:
  ci:
    runs-on: [1]
    steps:
      - uses: [2]
      - name: Install dependencies
        run: npm [3]

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

Aubuntu-latest

Bactions/checkout@v3

Cinstall

Dnode-latest

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect runner label.

Forgetting to checkout the code before installing.

Using wrong npm commands.

The job runs on ubuntu-latest. It checks out code using actions/checkout@v3. Then it installs dependencies with npm install.

Practice

1. What is the main purpose of setting up a CI pipeline for a Remix app?

easy

A. To write code faster without testing

B. To manually deploy the app to production

C. To create UI components automatically

D. To automatically run tests and build the app on code changes

Solution

1. Step 1: Understand CI pipeline purpose

   A CI pipeline runs tests and builds automatically when code changes happen.

2. Step 2: Identify correct purpose for Remix app

   This helps catch errors early and ensures the app builds correctly before deployment.

3. Final Answer:

   To automatically run tests and build the app on code changes -> Option D

4. Quick Check:

   CI pipeline = auto test and build [OK]

Hint: CI pipelines run tests/build automatically on code changes [OK]

Common Mistakes:

• Thinking CI deploys manually
• Assuming CI writes code
• Confusing CI with UI design

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

easy

A. when: push to main

B. trigger: push main

C. on: push: branches: [main]

D. event: push branch main

Solution

1. Step 1: Review GitHub Actions trigger syntax

   The correct YAML syntax uses 'on:' followed by the event 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 syntax.

3. Final Answer:

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

4. Quick Check:

   GitHub Actions trigger = on: push: branches: [main] [OK]

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

Common Mistakes:

• Using 'trigger' instead of 'on'
• Missing YAML indentation
• Writing event as plain text

3. Given this GitHub Actions step in a Remix CI pipeline:

      - name: Install dependencies
        run: npm install

What will happen when this step runs?

medium

A. It installs all npm packages listed in package.json

B. It removes all installed npm packages

C. It runs the Remix app without installing packages

D. It updates npm to the latest version

Solution

1. Step 1: Understand npm install command

   Running 'npm install' downloads and installs all dependencies listed in package.json.

2. Step 2: Match command effect to options

   It installs all npm packages listed in package.json correctly describes this behavior. Other options describe unrelated actions.

3. Final Answer:

   It installs all npm packages listed in package.json -> Option A

4. Quick Check:

   npm install = install dependencies [OK]

Hint: 'npm install' installs packages from package.json [OK]

Common Mistakes:

• Confusing install with uninstall
• Thinking it runs the app
• Assuming it updates npm itself

4. You wrote this GitHub Actions workflow snippet but the pipeline fails to start on pushes:

on:
  push:
    branch: main

What is the error causing the failure?

medium

A. The key 'branch' should be 'branches' (plural) in YAML

B. The 'on' keyword is misspelled

C. The indentation is incorrect for 'push' key

D. The workflow file must be named 'ci.yml' exactly

Solution

1. Step 1: Check YAML keys for GitHub Actions triggers

   The correct key to specify branches is 'branches' (plural), not 'branch'.

2. Step 2: Identify error in snippet

   Using 'branch' causes the trigger to be ignored, so the pipeline won't start on push.

3. Final Answer:

   The key 'branch' should be 'branches' (plural) in YAML -> Option A

4. Quick Check:

   Trigger key = branches (plural) [OK]

Hint: Use 'branches' not 'branch' for GitHub Actions push triggers [OK]

Common Mistakes:

• Using singular 'branch' instead of 'branches'
• Misnaming workflow files
• Incorrect indentation

5. You want your Remix app's CI pipeline to run tests only when files in the app/ directory change. Which GitHub Actions trigger configuration achieves this?

hard

A. on:
push:
branches: [main]
only: ["app/**"]

B. on:
push:
branches: [main]
paths: ["app/**"]

C. on:
push:
branches: [main]
include: ["app/**"]

D. on:
push:
branches: [main]
files: ["app/**"]

Solution

1. Step 1: Understand GitHub Actions path filters

   To trigger workflows only on changes in specific paths, use the 'paths' key under push.

2. Step 2: Identify correct syntax for filtering 'app/' directory

   on: push: branches: [main] paths: ["app/**"] uses 'paths: ["app/**"]' which matches all files in app/ and subfolders.

3. Final Answer:

   on: push: branches: [main] paths: ["app/**"] -> Option B

4. Quick Check:

   Use 'paths' to filter files in GitHub Actions triggers [OK]

Hint: Use 'paths' key to filter files triggering workflow [OK]

Common Mistakes:

• Using 'files' or 'only' instead of 'paths'
• Incorrect YAML indentation
• Missing quotes around path patterns