CI/CD workflow (GoogleChromeLabs/ProjectVisBug)

The CI/CD workflow from GoogleChromeLabs/ProjectVisBug, explained and optimized by Latchkey.

CI health: F - at risk

Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →

Source: GoogleChromeLabs/ProjectVisBug.github/workflows/main.ymlLicense Apache-2.0View source

What it does

This is the CI/CD workflow from the GoogleChromeLabs/ProjectVisBug repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)

name: CI/CD
on:
  push:
    branches:
      - main

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v1

      - name: Use Node.js 16.x
        uses: actions/setup-node@v1
        with:
          node-version: 16.x

      - name: Git Init
        run: |
          git switch -c main
          git config --global user.email "argyle@google.com"
          git config --global user.name "Adam Argyle"

      - name: Test & Build
        run: |
          npm install
          npm run extension:release

      - name: Git Push
        uses: ad-m/github-push-action@master
        continue-on-error: true
        with:
          tags: true
          branch: 'main'
          github_token: ${{ secrets.GITHUB_TOKEN }}

      - name: Save Build As Artifact
        uses: actions/upload-artifact@v4
        continue-on-error: true
        with:
          name: VisBug
          path: extension/build/visbug.zip

      - name: Publish Chrome Extension
        uses: trmcnvn/chrome-addon@v2
        continue-on-error: true
        with:
          extension: cdockenadnadldjbbgcallicgledbeoc
          zip: extension/build/visbug.zip
          client-id: ${{ secrets.CHROME_CLIENT_ID }}
          client-secret: ${{ secrets.CHROME_CLIENT_SECRET }}
          refresh-token: ${{ secrets.CHROME_REFRESH_TOKEN }}

      - name: Firebase Deploy
        uses: pizzafox/firebase-action@1.0.7
        env:
          PROJECT_ID: "visbug"
          FIREBASE_TOKEN: ${{ secrets.FIREBASE_TOKEN }}
        with:
          args: deploy

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

name: CI/CD
on:
  push:
    branches:
      - main
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v1
 
      - name: Use Node.js 16.x
        uses: actions/setup-node@v1
        with:
          cache: 'npm'
          node-version: 16.x
 
      - name: Git Init
        run: |
          git switch -c main
          git config --global user.email "argyle@google.com"
          git config --global user.name "Adam Argyle"
 
      - name: Test & Build
        run: |
          npm install
          npm run extension:release
 
      - name: Git Push
        uses: ad-m/github-push-action@master
        continue-on-error: true
        with:
          tags: true
          branch: 'main'
          github_token: ${{ secrets.GITHUB_TOKEN }}
 
      - name: Save Build As Artifact
        uses: actions/upload-artifact@v4
        continue-on-error: true
        with:
          name: VisBug
          path: extension/build/visbug.zip
 
      - name: Publish Chrome Extension
        uses: trmcnvn/chrome-addon@v2
        continue-on-error: true
        with:
          extension: cdockenadnadldjbbgcallicgledbeoc
          zip: extension/build/visbug.zip
          client-id: ${{ secrets.CHROME_CLIENT_ID }}
          client-secret: ${{ secrets.CHROME_CLIENT_SECRET }}
          refresh-token: ${{ secrets.CHROME_REFRESH_TOKEN }}
 
      - name: Firebase Deploy
        uses: pizzafox/firebase-action@1.0.7
        env:
          PROJECT_ID: "visbug"
          FIREBASE_TOKEN: ${{ secrets.FIREBASE_TOKEN }}
        with:
          args: deploy

What changed

Run on Latchkey managed runners with one line (runs-on), which apply the fixes below automatically and self-heal transient failures. This example uses latchkey-small; pick the runner size that fits the job.
Cancel superseded runs when a branch or PR gets a newer push.
Cache dependency installs on the setup step so they are served from cache.
Add a job timeout so a hung step cannot burn hours of runner time.

3 third-party actions are referenced by a movable tag. Pin them to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

Dependency installs

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow

actions/checkout actions/setup-node actions/upload-artifact