fix: hardwire runs-on label so workflows do not depend on org variable #5
Loading…
Reference in a new issue
No description provided.
Delete branch "release/v0.1.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The psa-systems Forgejo org does not have RUNS_ON_OPENSUSE_BASE_LATEST set as a variable, so ${{ vars.RUNS_ON_OPENSUSE_BASE_LATEST }} expanded to an empty string and every workflow run queued forever waiting for a runner with a blank label. Replaces the indirect lookup in both build-oci-image.yml and create-release.yml with the literal label opensuse-base-16.0-latest, which matches how the runners are registered (per docker repo desktop-0x/forgejo-runner-* configs).
Trade-off: the label is now repeated literally in two workflow files instead of centralised on the org. If the runner label scheme changes in future, both files have to be touched. Worth it right now to unblock the v0.1.0 release without round-tripping through the Forgejo UI.
The psa-systems Forgejo org does not have RUNS_ON_OPENSUSE_BASE_LATEST set as a variable, so ${{ vars.RUNS_ON_OPENSUSE_BASE_LATEST }} expanded to an empty string and every workflow run queued forever waiting for a runner with a blank label. Replaces the indirect lookup in both build-oci-image.yml and create-release.yml with the literal label opensuse-base-16.0-latest, which matches how the runners are registered (per docker repo desktop-0x/forgejo-runner-* configs). Trade-off: the label is now repeated literally in two workflow files instead of centralised on the org. If the runner label scheme changes in future, both files have to be touched. Worth it right now to unblock the v0.1.0 release without round-tripping through the Forgejo UI.