GitHub Actions usage scenarios

Below you will find a compendium with a selection of examples on how to use container images for the IAR Build Tools for Arm on GitHub Actions.

Fetch only the latest base image

jobs:
  job-name:
    runs-on: ubuntu-24.04
    container: ghcr.io/iarsystems/arm
    steps:
    # Job steps...

Fetch a base image with device support for a single vendor

Using a container from the base image with device support on GitHub Actions. In the example below <vendor> can be additional, base, infineon, microchip, nxp, renesas, st or ti.

jobs:
  job-name:
    runs-on: ubuntu-24.04
    container: ghcr.io/iarsystems/arm:9.70.4-<vendor>
    steps:
    # Job steps...

Fetch base images with device support from multiple vendors

Using a container from the base image with device support from multiple vendors on GitHub Actions. In the example below <vendorN> can be additional, base, infineon, microchip, nxp, renesas, st or ti.

jobs:
  job-name-1:
    runs-on: ubuntu-24.04
    container: ghcr.io/iarsystems/arm:9.70.4-<vendor1>
    steps:
    # Job steps...

  job-name-2:
    runs-on: ubuntu-24.04
    container: ghcr.io/iarsystems/arm:9.70.4-<vendor2>
    steps:
    # Job steps...

Fetch a minimalistic image

The minimalistic image is a lightweight variant from the base image that can be used for faster fetching. It comes only with the bare essentials: the compiler and its binary utilities. For icstat and iarbuild, use the -base image instead.

jobs:
  job-name:
    runs-on: ubuntu-24.04
    container: ghcr.io/iarsystems/arm:9.70.4-minimal
    steps:
    # Job steps...