Repository navigation
ci: run the post-merge light jobs on GKE runner pods - #592
Merged
Merged
Conversation
The secret-free light jobs of ci-post, corpus-parity and native-live (authz, changes, gates and the aggregates) move from the hosted image to bare gke-<size>-<arch> labels; promote-guard, docs-post and the release probe authz follow where the per-label cap of eight allows. ci-post's seven light jobs take gke-2cpu-4gb-amd64, native-live and corpus-parity's five take gke-4cpu-8gb-amd64. fleet-post-capability.yml is retired. docs/ci.md replaces sentences by name: - 3ea5a0d: "Hosted ubuntu-24.04 runs all eight authz jobs, both CI changes/build-gate jobs, all post/native aggregates and docs.yml's build". - b0f4341: "These light, secret-free jobs need no VM-only tools, mounts or caches". - c85a40b: "Hosted exceptions include the named light jobs and the existing release/promotion pins"; "The four amd64 post legs, arm64 cells, preflight, parity and native verification use gke-runners; their aggregates use the light image"; "Light jobs and four aggregates"; "authz: hosted ubuntu-24.04"; "authz and both aggregates: hosted ubuntu-24.04"; "GKE jobs start only from ci-post.yml, corpus-parity.yml and native-live.yml at refs/heads/main". The promotion-guard workflow-env test also expects the two credential findings that promote-guard on a pod now raises. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
Comment on lines
+3460
to
+3461
| 'promote-baseline.yml job promote-guard must keep production credentials ' | ||
| 'on a hosted standard runner', |
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.
Replaces #582 as one commit on current main.
The secret-free light jobs of ci-post, corpus-parity and native-live (authz,
changes, gates and the aggregates) move from the hosted image to bare
gke-- labels; promote-guard, docs-post and the release probe authz
follow where the per-label cap of eight allows. ci-post's seven light jobs take
gke-2cpu-4gb-amd64, native-live and corpus-parity's five take gke-4cpu-8gb-amd64.
fleet-post-capability.yml is retired.
docs/ci.md replaces sentences by name:
jobs, all post/native aggregates and docs.yml's build".
release/promotion pins"; "The four amd64 post legs, arm64 cells, preflight, parity
and native verification use gke-runners; their aggregates use the light image";
"Light jobs and four aggregates"; "authz: hosted ubuntu-24.04"; "authz and both
aggregates: hosted ubuntu-24.04"; "GKE jobs start only from ci-post.yml,
corpus-parity.yml and native-live.yml at refs/heads/main".
The promotion-guard workflow-env test also expects the two credential findings
that promote-guard on a pod now raises.
🤖 Generated with Claude Code