Open
Labels
area:buildCI/CD workflows, releases, build targets, packaging, and artifact publication.CI/CD workflows, releases, build targets, packaging, and artifact publication.topic:dxMaking OpenShell easy to contribute to for humans and agents.Making OpenShell easy to contribute to for humans and agents.
Description
User Story
I maintain OpenShell's CI. Release Dev runs on every commit to main, and I want the dev release and its integration results to arrive sooner.
Description
Release Dev has the same delays that #5268 removes from Branch E2E:
- Images, DEB, RPM, snap, prepare-integration, docker-e2e and vm-e2e all wait on the macOS rows of
build-binaries, and the DEB build waits on the macOS VM driver. In run 41869061590 the macOS gateway finished 3 minutes after the Linux gateway. - Prepare tmachine inputs builds the test archives, test workload images and Helm chart after the packages finish. Prepare took 4 to 7 minutes in recent runs.
Use the linux/macos inputs and the early test-inputs job from #5268 in release-dev.yml.
Context
- Release Dev runs only on pushes to main, so this change can't be fully exercised before merge. Keep it in its own PR so it can be reverted independently.
publish-snapandpackage-binariesmust also wait on the macOS builds. Otherwise a macOS build failure would no longer block them.release-build.yml(stable Release and Pre-release) is out of scope.
Definition of Done
- Release Dev Linux consumers don't wait on macOS builds.
- A macOS build failure still blocks the dev release, the snap publish and the binary packaging.
- The first Release Dev run on main after merge succeeds, with before/after timings recorded.
Metadata
Metadata
Assignees
Labels
area:buildCI/CD workflows, releases, build targets, packaging, and artifact publication.CI/CD workflows, releases, build targets, packaging, and artifact publication.topic:dxMaking OpenShell easy to contribute to for humans and agents.Making OpenShell easy to contribute to for humans and agents.
Activity