[hibernate-commits] [hibernate/hibernate-orm] 02574e: Run CI reporting even when the CI workflow was can...

Branch: refs/heads/main Home: https://github.com/hibernate/hibernate-orm Commit: 02574e1d4e0f903069ecfb428eb30b8a9e407bc7 https://github.com/hibernate/hibernate-orm/commit/02574e1d4e0f903069ecfb4... Author: Yoann Rodière <yoann(a)hibernate.org&gt; Date: 2026-06-18 (Thu, 18 Jun 2026) Changed paths: M .github/workflows/ci-report.yml Log Message: ----------- Run CI reporting even when the CI workflow was cancelled When a single job times out (e.g. the TCK job hitting the 6-hour limit), GitHub marks the entire workflow as cancelled. The previous condition skipped reporting in that case, which meant build scan artifacts from all the jobs that did complete successfully were never published to Develocity. This caused the Develocity Build Scans check to miss all GH Actions build scans for PRs. Also make the publish loop best-effort: individual publish failures (e.g. when the PR branch uses a different Develocity plugin version than main, producing incompatible build-scan-data) are logged as warnings instead of failing the job. This was already a pre-existing issue visible in ci-report runs. See https://github.com/hibernate/hibernate-github-bot/issues/399 Assisted-By: Claude Code <noreply(a)anthropic.com&gt; Commit: 267a3f6b88227ce193370db288ff13d29498d917 https://github.com/hibernate/hibernate-orm/commit/267a3f6b88227ce193370db... Author: Yoann Rodière <yoann(a)hibernate.org&gt; Date: 2026-06-18 (Thu, 18 Jun 2026) Changed paths: M .github/workflows/ci-report.yml Log Message: ----------- Resolve PR target branch for build scan publishing The publish-build-scans job was always checking out the default branch (via github.ref), but the build scan data format is tied to the Develocity plugin version used during the CI build. When a PR targets a non-default branch (e.g. 7.3) that uses a different plugin version than main, buildScanPublishPrevious fails with "no previous build data" because it cannot read the data format. Resolve the PR's target branch (or the pushed branch for push events) and check that out instead, matching what publish-sonar-scans already does. Also update the cache key to use the resolved branch. Assisted-By: Claude Code <noreply(a)anthropic.com&gt; Compare: https://github.com/hibernate/hibernate-orm/compare/4f1746a10271...267a3f6... To unsubscribe from these emails, change your notification settings at https://github.com/hibernate/hibernate-orm/settings/notifications