ci: add concurrency control and JVM crash diagnostics to publish workflow - #150
Merged
Merged
Conversation
Mirrors workspace/policies/ci-test-diagnostics.md section 3.1: a failure-gated step that prints hs_err_pid*.log (first 200 lines) and the surefire dumpstream/dump into the job log, ahead of the existing crash-dumps upload. An artifact-only crash log is unreadable wherever egress to Azure Blob Storage is denied, and GitHub serves artifact bytes from nowhere else. Paths are repo-root-relative here, matching this repo's single-module layout and the existing upload's globs. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AnNYn8W1xuVxVJtyL34GyH
…de stale CI runs Two CI-hygiene changes, applied identically across the four Java repos. 1. "Print crash logs (on failure)" ran on `if: failure()` -- so on EVERY red job, the overwhelming majority of which are ordinary assertion failures that never write a crash log. It nonetheless printed "The fork died without the JVM writing a crash log", stated as fact, under a heading that also echoed perfectly healthy server logs. Reading a normal test failure, that is an invented crash to chase. It now reports the observation, says plainly that no file is the EXPECTED case for a normal failure, and names the one signature -- "The forked VM terminated without properly saying goodbye", or an exit with no test results -- that would actually justify the JVM-abort conclusion. 2. `publish.yml` had no `concurrency:` group, so every push started a full parallel pipeline while superseded ones kept draining; four were live at once in one session, which makes "what is CI saying right now" ambiguous and wastes runner time on results nobody reads. `cancel-in-progress` is scoped to `pull_request` ONLY: a push to main or a v* tag is a release path and cancelling one midway could leave a partially published artifact set, so those always run to completion. Verified: every touched workflow parses with the expected concurrency mapping. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AnNYn8W1xuVxVJtyL34GyH
bernardladenthin
had a problem deploying
to
startgate
August 29, 2026 15:07 — with 
GitHub Actions
Error
GitHub Actions
Error
bernardladenthin
had a problem deploying
to
maven-central
August 29, 2026 15:07 — with
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
maven-central
August 29, 2026 15:07 — with
GitHub Actions
Failure
GitHub Actions
Failure
|
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
2 participants
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.
Summary
concurrencyconfiguration to cancel in-flight PR runs when a branch is pushed again, reducing wasted runner time and CI ambiguity. Release paths (main/v* tags) always run to completion to avoid partial artifact publication.hs_err_pid*.logand surefire dump/dumpstream files to the run page on failure, making JVM-level aborts readable without requiring artifact downloads from restricted networks.Test plan
Related issues / PRs
References
../workspace/policies/ci-test-diagnostics.mdsection 3.1 for crash log handling rationale.Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.mdhttps://claude.ai/code/session_01AnNYn8W1xuVxVJtyL34GyH