Repository navigation
Split landed CI and native builds onto GKE pods - #162
Merged
Merged
Conversation
ci.yml and native-feed.yml now trigger on pull_request only and keep their hosted jobs, displayed names and required checks unchanged. The new ci-post.yml and native-feed-post.yml run on push to main and workflow_dispatch: authz and a main-ref guard stay hosted, the proof jobs take bare scalar GKE labels sized from their needs, and one hosted aggregate keeps the name `check`. database-e2e and the macOS leg stay hosted. docs.yml is unchanged because the Pages actions have no verified immutable pins. The release evidence reader and the recovery query now follow the landed run to ci-post.yml, and pin the exact bytes of both workflow files. Replaced documentation sentences (docs/releasing.md): - "The App's merge triggers ordinary main CI." is now "The App's merge triggers ci-post.yml on main." - "The landed main CI still authorizes the exact wheel/sdist bytes used by the existing publisher." is now "The landed ci-post.yml run authorizes the exact wheel/sdist bytes used by the existing publisher." Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Wrap the over-long upload-artifact pin line (E501) and write the ci-post.yml match pattern as a raw escaped string (RUF043). No behaviour change. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
No run before merge shows a working Docker daemon on a gke-4cpu-8gb-amd64 pod, and a red main on this repository blocks the next release upload. Both jobs go back to ubuntu-24.04 (with PF_CI_LABELS to match); their steps, including the docker info check, are unchanged. The reviewed ci-post.yml digest in the release evidence reader and the route table in the post-merge workflow test follow. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…a pod The runner row of test_post_ci_control_rejects_reverting_a_proof set the Distribution job to ubuntu-24.04, which is now its correct runner, so the mutation no longer changed anything and the control did not raise. It now sets the ready job, which must stay on a pod, to the hosted runner. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Splits CI so that pull requests keep running on hosted runners and post-merge runs (push to main and manual dispatch) go to GKE runner pods.
ci.ymlruns on pull requests only, on the standard hosted label.ci-post.ymlruns the same jobs on baregke-<size>-<arch>pods. Jobs that need the runner's Docker (PostgreSQL service, testcontainers) or other hosted-only features stay hosted.The org policy checker reports no added findings against main.
🤖 Generated with Claude Code