Skip to content

merge queue: checking main (0199bd5) and #12416 together - #12481

Closed
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/9d63494c7c
Closed

merge queue: checking main (0199bd5) and #12416 together#12481
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/9d63494c7c

Conversation

@mergify

@mergify mergify Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (0199bd5) and #12416 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #12416.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 0199bd5e6cbc744772a640a194caaca5167b9db9
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12416
    scopes: []
scopes: []
...

jd and others added 3 commits August 18, 2026 09:18
The CI Insights setup pages and the two matrix helpers disagreed with each other
about how to override the job name a test report is filed under, and none of
them said where the default comes from.

The three setup pages now name `MERGIFY_TEST_JOB_NAME` — the variable the CLI
reads, and the one every framework plugin (pytest, rspec, vitest) already
documents — say where the default comes from on each provider (`GITHUB_JOB` on
GitHub Actions, Jenkins' own `JOB_NAME`, the step label on Buildkite), and show
where to set it. They also state why it matters: the job name is part of a
test's identity, so a scheduled run that reports a different name splits its
results off from the pull request ones.

The GitHub Actions matrix case is stated the way it actually breaks: every leg
of a matrix reports the same job name because they share one `GITHUB_JOB`. The
old text left the reader to infer why an override was needed at all.

The two matrix helpers keep recommending the native override — the action's
`job_name` input and the Buildkite plugin's `job_name` property. Both currently
export `MERGIFY_JOB_NAME`, which no uploader reads, so neither takes effect
today; that is a bug in the three producers of that variable, not something the
docs should route readers around. Fixing them is tracked separately, and the
snippets pin moving tags (the action's `v25`, the plugin's `#v1`), so readers
pick the fix up when those tags move.

The pytest, rspec and vitest pages already agreed with this and are unchanged.

Settles Mergifyio/ci-bot#369.
Part of MRGFY-8720

Change-Id: I96e06bb4500bf9e7664d36d941ef0d962004e9a9
The JUnit and TestNG recipes told Gradle users to configure their report output
with a `reports { junitXml.enabled = true; junitXml.destination = ... }` block.
Gradle 8.0 removed both of those properties ("The deprecated `destination`, and
`enabled` properties of the `Report` type have been removed", per Gradle's own
upgrade notes), so on any current Gradle that block fails the build. A reader
following either page was stopped at the very first step, before ever reaching
the upload step.

Nothing needs to replace it. Gradle's `test` task already writes JUnit XML to
`build/test-results/test/`, which is the path both pages then tell the reader to
upload, so the block was configuring the default. It goes, the default location
is stated instead, and only the line that does have to be there stays:
`useJUnitPlatform()` for JUnit 5, `useTestNG()` for TestNG.

That also settles the version question the recipe would otherwise have to
answer, since `useJUnitPlatform()` and `useTestNG()` are accepted by every
Gradle version anyone is running.

Settles Mergifyio/ci-bot#370. The same broken block was in the TestNG recipe,
which that issue did not mention.
Part of MRGFY-8720

Change-Id: I24b7f2d8324397dd1371a46550777fc658995b54
@mergify
mergify Bot deployed to Mergify Merge Protections August 21, 2026 14:43 Active
@mergify mergify Bot closed this Aug 21, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/9d63494c7c branch August 21, 2026 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant