Skip to content

Versioned releases and SBOMs for partner runner images #160

@ubiratansoares

Description

@ubiratansoares

Type of issue

  • Error when running a workflow.
  • Request for additional tools or software for an existing image.
  • Request for a new image, Linux or Windows.
  • Other

Describe the issue
As of the time this issue is being filled, Runner images provided by Github are versioned (example), and are frequently updated. In addition to that, Github provides SBOMs describing the whole suite of installed software in a given Runner image. This artifact eventually makes it easier to troubleshoot whether some CI failure was introduced by some software component update in the latest image release, even whether minor or patch, since we can always refer to different versions of the runner image as per setup job step of a given Workflow, getting versions of images used in different commits or workflow runs, and diff SBOMs.

Right now, partner runner images, especially ARM, do not follow this approach, which makes it hard to troubleshoot whether CI failures eventually are attached to some software component that differs by some versions between aarch64 images and it x86_64 counterpart.

To Reproduce
N/A

Expected behavior
We should have versioned releases of partner runner images, alongside with SBOMs, as we have with Github provided images. Ideally, we should also have the changelog regarding what changed between image releases.

Screenshots
N/A

Desktop (please complete the following information):

  • OS: Ubuntu 22.04 and Ubuntu 24.04

Additional context
N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions