Blob storage website CI workflow (AMAI-GmbH/AI-Expert-Roadmap)

The Blob storage website CI workflow from AMAI-GmbH/AI-Expert-Roadmap, explained and optimized by Latchkey.

What it does

This is the Blob storage website CI workflow from the AMAI-GmbH/AI-Expert-Roadmap repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

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

The workflow

# This is a basic workflow to help you get started with Actions

name: Blob storage website CI

# Controls when the action will run. Triggers the workflow on push or pull request
# events but only for the main branch
on:
  push:
    branches: [ main ]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - name: Use Node.js
      uses: actions/setup-node@v1
      with:
        node-version: '22'
    - run: npm install
    - run: npm run build --if-present
      env:
        CI: true
    - name: Azure Login
      uses: azure/login@v1
      with:
        creds: ${{ secrets.AZURE_CREDENTIALS }}
    - name: Upload to Azure
      uses: azure/CLI@v1
      with:
        azcliversion: 2.33.0
        inlineScript: |
          az storage blob upload-batch -s public/roadmap -d \$web/roadmap --account-name iamai --content-cache-control 'public,max-age=3600'
    - name: Purge Azure CDN
      uses: azure/CLI@v1
      with:
        azcliversion: 2.33.0
        inlineScript: |
          az cdn endpoint purge --content-paths  "/*" --profile-name "i-am-ai" --name "i-am-ai" --resource-group "Productive"
        # Azure logout 
    - name: Azure Logout
      uses: azure/CLI@v1
      with:
        azcliversion: 2.33.0
        inlineScript: |
          az logout
          az cache purge
          az account clear

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.

# This is a basic workflow to help you get started with Actions
 
name: Blob storage website CI
 
# Controls when the action will run. Triggers the workflow on push or pull request
# events but only for the main branch
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@v2
    - name: Use Node.js
      uses: actions/setup-node@v1
      with:
        cache: 'npm'
        node-version: '22'
    - run: npm install
    - run: npm run build --if-present
      env:
        CI: true
    - name: Azure Login
      uses: azure/login@v1
      with:
        creds: ${{ secrets.AZURE_CREDENTIALS }}
    - name: Upload to Azure
      uses: azure/CLI@v1
      with:
        azcliversion: 2.33.0
        inlineScript: |
          az storage blob upload-batch -s public/roadmap -d \$web/roadmap --account-name iamai --content-cache-control 'public,max-age=3600'
    - name: Purge Azure CDN
      uses: azure/CLI@v1
      with:
        azcliversion: 2.33.0
        inlineScript: |
          az cdn endpoint purge --content-paths  "/*" --profile-name "i-am-ai" --name "i-am-ai" --resource-group "Productive"
        # Azure logout 
    - name: Azure Logout
      uses: azure/CLI@v1
      with:
        azcliversion: 2.33.0
        inlineScript: |
          az logout
          az cache purge
          az account clear
 

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.

2 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