Week 13 - Systems

Introduction

Setting up your local environment

Continuous integration

Docker

Continuous Delivery

Cloud Computing

Continuous deployment

Chapter 3

Practice

Assignment

• Teachers

Back to core program

Under construction

<aside> 🚧

This page is currently under construction. Please check back later.

</aside>

• Create new branch
• Create file .github/workflows/integration.yml

name: Integration

# When shall we run this workflow?
on:
  push:
    branches:
      - main
  pull_request:
    branches:
      - main

jobs:
  lint:
    runs-on: ubuntu-latest

    steps:
      - name: Check out code
        uses: actions/checkout@v4

      - name: Set up Node.js
        uses: actions/setup-node@v1
        with:
          node-version: '22'  # Specify your Node.js version

      - name: Install dependencies
        run: npm ci

      - name: Run Lint
        run: npm run lint:ci  # Run your linting command

• git commit/push open PR
• Check the lint action

• IT FAILED TADA

Let’s fix it

• Run locally npm run lint
• run git status → it updated our new yaml file
• git add/commit/push

Let’s merge it

What to learn from this?

Imagine you are not alone anymore to work on your project and you want everyone to have the same code styling to ensure your code base remain easy to maintain and read from everyone.

Using Pull Request with automation such as the one we just did will make sure any code that is added to the main branch passed all the same exact steps and tests.

This is what we call the “Integration” part, literally, it means integrating new code into the code base, ensuring the new code follows the same rules than the rest of the code base.

You will find different projects runs different checks as part of their integration steps but in general you will find those 3 main ones:

• Linter - ensure the code itself follows the project standard
• Tests - Ensure the new code do not breaks existing functionality and that the new code comes with tests for itself
• Build/package - Ensure we are able to fully build / compile / package the software with the new code

*https://hackyourfuture.net/*

Found a mistake or have a suggestion? Let us know in the feedback form.