CI/CD Pipelines for Angular

1. Introduction

Continuous Integration and Continuous Deployment (CI/CD) are vital practices in modern software development, especially for frameworks like Angular. This lesson will guide you through the process of setting up a CI/CD pipeline for your Angular applications.

2. What is CI/CD?

CI/CD is a method to automate the software delivery process. It consists of two main components:

• Continuous Integration (CI): Automates the integration of code changes from multiple contributors into a single software project.
• Continuous Deployment (CD): Automates the release of new software versions to users after a successful build and test process.

3. Setting Up CI/CD for Angular

To set up a CI/CD pipeline for an Angular application, follow these steps:

3.1 Prerequisites

• Node.js and npm installed.
• An Angular application created using Angular CLI.
• A version control system (e.g., Git) to manage your source code.
• A CI/CD service (e.g., GitHub Actions, GitLab CI, CircleCI).

3.2 Create a Git Repository

Initialize your Angular app in a Git repository by running:

git init

3.3 Setting Up CI with GitHub Actions

Create a file named .github/workflows/ci.yml in your repository:

name: CI

on:
  push:
    branches:
      - main

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Setup Node.js
        uses: actions/setup-node@v2
        with:
          node-version: '14'

      - name: Install dependencies
        run: npm install

      - name: Run tests
        run: npm test

3.4 Setting Up CD

Extend the previous workflow to include deployment. For example, to deploy to Firebase, add this to your ci.yml:

      - name: Build
        run: npm run build --prod

      - name: Deploy to Firebase
        uses: wzieba/Firebase-Hosting-Github-Action@v2.2.0
        with:
          firebaseServiceAccount: ${{ secrets.FIREBASE_SERVICE_ACCOUNT }}
          channelId: live

4. Best Practices

• Write clear and concise commit messages.
• Run tests before deploying.
• Keep your CI/CD configurations under version control.
• Monitor your pipeline and set up alerts for failures.

5. FAQ