[Bug]: CI fails on forks

[jsoref]

I have done the following

• I have searched the existing issues
• If possible, I've reproduced the issue using the 'main' branch of this project

Steps to reproduce

1. Fork this repository in a user/org with actions enabled
2. Update the fork
3. See action is stuck in queued state

Current behavior

Action will be queued for 6 hours https://github.com/jsoref/container/actions/runs/15662746312 until GitHub's timeout (or I decide to cancel the workflow run)

Expected Behavior

use an if: on the job level that relies on either a vars.HAS_X_RUNNER (to let others set up runners if they're so inclined), github.repository to limit the job to only run in the apple repository, or define a fallback runner that would work in forks.

Environment

GitHub Actions - GitHub Fork

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[makhov]

It runs on self-hosted runners, so yeah, it hangs on forks, because they don't have any.

    runs-on: [self-hosted, macos, sequoia, ARM64]

I think runners are preconfigured, which helps to run builds faster. I agree, it would be nice to run workflows on GitHub-hosted runners, but it means that on each build Xcode will be downloaded, which is 2.7Gb. The free GHA limits will be hit very fast, I think, so not sure if it worth it

[jsoref]

Right. If it's infeasible to get it working with normal runners, then either an if for this repository or an if for vars which would let people opt in if they're willing to configure their own self-hosted runners. My guess is it's fairly unlikely anyone else would set up such runners, in which case the simple if for this repository makes sense.

If you're amenable, I could make that PR...

[katiewasnothere]

@jsoref Unfortunately the GitHub provided runners' OS version does not meet the project's requirements for building and running (last I checked). Could you give me an example of what the option using vars.HAS_X_RUNNER would look like? Just so I understand.

[jsoref]

@katiewasnothere that's understandable. Here you go:

You'd go to https://github.com/apple/container/settings/variables/actions/new and create HAS_ARM64_SEQUOIA_RUNNER with a value (1 is fine, anything that's truthy will work).

If the runners are org runners instead of repo runners, you'd use https://github.com/organizations/apple/settings/variables/actions/new instead.

container/.github/workflows/common.yml

Line 15 in 555dbfc

runs-on: [self-hosted, macos, sequoia, ARM64]

      runs-on: [self-hosted, macos, sequoia, ARM64]
+     if: vars.HAS_ARM64_SEQUOIA_RUNNER

You can name the variable whatever you like as long as the repos/org have it before you add the condition.

[JLesDev]

The names shouldn't matter but in line with what others have said the project requirements are different for building and running. Do you have more information about the specific details or your process?