Skip to content
Latchkey

build-hermesc-apple workflow (facebook/hermes)

The build-hermesc-apple workflow from facebook/hermes, explained and optimized by Latchkey.

A

CI health: A - excellent

Run this on Latchkey for self-healing, caching, and up to 58% lower cost.

Grade your own workflow free or run it on Latchkey →
Source: facebook/hermes.github/workflows/build-hermesc-apple.ymlLicense MITView source

What it does

This is the build-hermesc-apple workflow from the facebook/hermes 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

workflow (.yml)
name: build-hermesc-apple

on: workflow_call

jobs:
  build-hermesc-apple:
    runs-on: macos-15
    steps:
      - name: Checkout
        uses: actions/checkout@v4
      - name: Setup xcode
        uses: ./.github/actions/setup-xcode
      - name: Build HermesC Apple
        shell: bash
        run: ./utils/build-apple-framework.sh build_hermesc
      - name: Upload HermesC Artifact
        uses: actions/upload-artifact@v4.3.4
        with:
          name: hermesc-apple
          path: ./build_host_hermesc

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: build-hermesc-apple
 
on: workflow_call
 
jobs:
  build-hermesc-apple:
    timeout-minutes: 30
    runs-on: macos-15
    steps:
      - name: Checkout
        uses: actions/checkout@v4
      - name: Setup xcode
        uses: ./.github/actions/setup-xcode
      - name: Build HermesC Apple
        shell: bash
        run: ./utils/build-apple-framework.sh build_hermesc
      - name: Upload HermesC Artifact
        uses: actions/upload-artifact@v4.3.4
        with:
          name: hermesc-apple
          path: ./build_host_hermesc
 

What changed

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