ci: run Check on the dev runner label #141

Merged
Claude-Run merged 1 commit from chore/YT-86-check-dev-runner-label into main 2026-08-02 02:00:13 +02:00
Member

The check job compiled Rust natively on RUNS_ON_OPENSUSE_BASE_LATEST, whose image has no C toolchain, so it carried an "Ensure a C toolchain" step that probed for zypper / apt-get / apk / dnf and installed gcc on every run. The runner labels already split by what a job does: RUNS_ON_OPENSUSE_DEV_LATEST is the image that ships cc / gcc / ld plus the glibc and OpenSSL headers ring and libsqlite3-sys need. Request that label and delete the install step rather than re-solving the image's job on every run.

Every runs-on in .forgejo/workflows/ now carries a comment justifying its label: check.yml compiles on the runner (dev), build-linux.yml and build-windows.yml compile inside docker buildx (base), create-release.yml only runs git and one HTTP call (base), and build-macos.yml sits outside the OpenSUSE split on RUNS_ON_MACOS with its Xcode probe.

crates/yt-cli/tests/ci_runner_labels.rs enforces all three properties mechanically, so the fallback cannot come back unnoticed.

#YT-86

The check job compiled Rust natively on RUNS_ON_OPENSUSE_BASE_LATEST, whose image has no C toolchain, so it carried an "Ensure a C toolchain" step that probed for zypper / apt-get / apk / dnf and installed gcc on every run. The runner labels already split by what a job does: RUNS_ON_OPENSUSE_DEV_LATEST is the image that ships cc / gcc / ld plus the glibc and OpenSSL headers ring and libsqlite3-sys need. Request that label and delete the install step rather than re-solving the image's job on every run. Every runs-on in .forgejo/workflows/ now carries a comment justifying its label: check.yml compiles on the runner (dev), build-linux.yml and build-windows.yml compile inside docker buildx (base), create-release.yml only runs git and one HTTP call (base), and build-macos.yml sits outside the OpenSUSE split on RUNS_ON_MACOS with its Xcode probe. crates/yt-cli/tests/ci_runner_labels.rs enforces all three properties mechanically, so the fallback cannot come back unnoticed. #YT-86
ci: run Check on the dev runner label
All checks were successful
Check / fmt + clippy + build + tests (pull_request) Successful in 32s
Create release / Create release from merged PR (pull_request) Has been skipped
b044b679a3
The check job compiled Rust natively on RUNS_ON_OPENSUSE_BASE_LATEST, whose image has no C toolchain, so it carried an "Ensure a C toolchain" step that probed for zypper / apt-get / apk / dnf and installed gcc on every run. The runner labels already split by what a job does: RUNS_ON_OPENSUSE_DEV_LATEST is the image that ships cc / gcc / ld plus the glibc and OpenSSL headers ring and libsqlite3-sys need. Request that label and delete the install step rather than re-solving the image's job on every run.

Every runs-on in .forgejo/workflows/ now carries a comment justifying its label: check.yml compiles on the runner (dev), build-linux.yml and build-windows.yml compile inside docker buildx (base), create-release.yml only runs git and one HTTP call (base), and build-macos.yml sits outside the OpenSUSE split on RUNS_ON_MACOS with its Xcode probe.

crates/yt-cli/tests/ci_runner_labels.rs enforces all three properties mechanically, so the fallback cannot come back unnoticed.

#YT-86
Claude-Run deleted branch chore/YT-86-check-dev-runner-label 2026-08-02 02:00:13 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pandoras-box/youtrack-cli!141
No description provided.