ci(pipeline): guard integration/e2e jobs when LLM secrets unavailable #10996

Open
HAL9000 wants to merge 3 commits from fix/9222-guard-integration-e2e-jobs into master

3 Commits

Author SHA1 Message Date
HAL9000 8c43c5fdf9 fix(ci): address reviewer feedback on guard steps and BDD tests
CI / push-validation (pull_request) Successful in 27s
CI / lint (pull_request) Successful in 39s
CI / build (pull_request) Successful in 40s
CI / helm (pull_request) Successful in 1m4s
CI / quality (pull_request) Successful in 1m6s
CI / typecheck (pull_request) Successful in 1m22s
CI / security (pull_request) Successful in 1m23s
CI / unit_tests (pull_request) Failing after 1m23s
CI / coverage (pull_request) Has been skipped
CI / docker (pull_request) Has been skipped
CI / e2e_tests (pull_request) Failing after 3m17s
CI / integration_tests (pull_request) Successful in 10m10s
CI / status-check (pull_request) Failing after 0s
- Fix YAML indentation on status-check job key (3-space → 4-space)
- Add id: secret-guard to integration_tests and e2e_tests guard steps
- Replace exit 0 with GITHUB_OUTPUT secrets_present output so subsequent
  nox steps can be conditionally skipped via if: expressions
- Add if: steps.secret-guard.outputs.secrets_present == 'true' to nox
  run steps and artifact upload steps in both jobs
- Replace broken needs.$job.result for-loop with explicit per-job
  expressions (needs.integration_tests.result / needs.e2e_tests.result)
- Merge duplicate ### Fixed sections in CHANGELOG [Unreleased]; fix
  issue reference from #9222 to #9128
- Add Background: block to BDD feature so all scenarios share the
  Given setup step; update guard scenarios to match new mechanism
- Remove unused import re from BDD step file; update step assertions
  to verify GITHUB_OUTPUT writes and explicit result expressions

ISSUES CLOSED: #9128
2026-06-14 13:38:28 -04:00
controller-ci-rerun 72914ad03c chore: re-trigger CI [controller] 2026-06-14 13:36:48 -04:00
HAL9000 d00e0add4c fix(ci): guard integration/e2e jobs when LLM secrets unavailable
Add LLM key verification steps to integration_tests and e2e_tests CI
jobs. When Anthropic/OpenAI/Google API keys are not configured, these
jobs skip gracefully with an informative message instead of failing.

Update status-check to treat skipped results from integration_tests and
e2e_tests as acceptable (only fail on failure/cancelled), while keeping
strict success-only requirements for core jobs (lint, typecheck, security,
quality, unit_tests, coverage, build, docker, helm, push-validation).

Add BDD tests verifying the guard mechanism exists and behaves correctly.

ISSUES CLOSED: #9222
2026-06-14 13:36:48 -04:00