Skip to content

ci: gate main merges with full Enterprise CLI suite - #56

Open
JacobPEvans-personal wants to merge 7 commits into
test/enterprise-write-lifecyclefrom
ci/enterprise-main-gate
Open

ci: gate main merges with full Enterprise CLI suite#56
JacobPEvans-personal wants to merge 7 commits into
test/enterprise-write-lifecyclefrom
ci/enterprise-main-gate

Conversation

@JacobPEvans-personal

@JacobPEvans-personal JacobPEvans-personal commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

What

  • make the 3.10–3.14 matrix a required prerequisite for a main-only splunk/splunk:latest Enterprise gate
  • run 61 catalogued reads, 91 ordinary write lifecycles, restart/reconnect, and cleanup verification as named CLI phases
  • remove the bespoke readiness script in favor of the image health check; publish JUnit failure summaries and failure-only logs, metadata, audit, and inventory
  • add a manual Python-only Cloud read canary, weekly ACS public-contract check, and PowerShell-ready operator documentation
  • make an empty optional SPLUNK_ACS_BASE_URL use the commercial default

Proof

Fresh local Splunk 10.4 container: 61 reads passed; 91 ordinary writes passed; restart observed a disconnect then reconnected in 38 seconds; 21 cleanup checks passed. Full local gate: 873 passed, 181 intentionally gated integration skips; ruff, format, pyright, commit and pre-push hooks all passed.

The manual CI dispatch on this branch is the final x86 / GitHub-hosted proof before merge.

Post-review updates

  • The Enterprise job now also runs on code pull requests (paths-filtered via
    dorny/paths-filter) so it can block a merge, with a splunkd service
    health check gating the steps; write count is 92 ordinary lifecycles after
    deploy-server serverclass delete landed in the stack.
  • Manual follow-up (admin): add Enterprise / Full CLI as a required
    status check on main branch protection. Skipped runs on docs-only PRs
    satisfy the requirement automatically.

@JacobPEvans-personal JacobPEvans-personal added the human:ready Ready for human review label Jul 31, 2026
…s check

- Wait for splunkd via a service-container health check instead of racing
  Splunk 10 first-boot.
- Run the Enterprise job on code pull requests (paths-filtered) as well as
  main pushes and manual dispatch, so it can actually block a merge.
- Accept a restart that completes inside one poll window; only failing to
  reconnect within the budget fails the test.
- Delete the orphaned integration smoke test (subset of the catalog suites)
  and drop the serverclass exclusion from the leak sweep now that
  serverclass delete exists.
- Hoist SPLUNK_WRITE_TEST to job env, cache uv, import the CLI normally in
  the restart loop, and align README/CHANGELOG counts and wording.

Assisted-by: Claude:claude-fable-5
Claude-Session: https://claude.ai/code/session_0117oTjSHHjg1nh28LGRZ7My
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

human:ready Ready for human review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant