Skip to content

ci: run the post-merge light jobs on GKE runner pods - #582

Closed
luisleo526 wants to merge 1 commit into
mainfrom
ci/gke-light-jobs
Closed

luisleo526 wants to merge 1 commit into
mainfrom
ci/gke-light-jobs

Conversation

@luisleo526

Copy link
Copy Markdown
Collaborator

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:

  • 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.

🤖 Generated with Claude Code

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]>
Comment on lines +3373 to +3374
'promote-baseline.yml job promote-guard must keep production credentials '
'on a hosted standard runner',
@luisleo526

Copy link
Copy Markdown
Collaborator Author

Superseded by #592 (same change as one commit on current main).

@luisleo526 luisleo526 closed this Oct 27, 2026
luisleo526 added a commit that referenced this pull request Oct 28, 2026
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-<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.



🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant