Skip to content

Update dependency org.jenkins-ci.plugins:junit to v1380#11335

Merged
MarkEWaite merged 2 commits intomasterfrom
renovate/org.jenkins-ci.plugins-junit-1380.x
Dec 17, 2025
Merged

Update dependency org.jenkins-ci.plugins:junit to v1380#11335
MarkEWaite merged 2 commits intomasterfrom
renovate/org.jenkins-ci.plugins-junit-1380.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 23, 2025

This PR contains the following updates:

Package Change Age Confidence
org.jenkins-ci.plugins:junit 1361.vfed194a_de34a_ -> 1380.v491ff054cd35 age confidence

Release Notes

jenkinsci/junit-plugin (org.jenkins-ci.plugins:junit)

v1380.v491ff054cd35

Compare Source

🚀 New features and improvements
👻 Maintenance
📦 Dependency updates

v1372.vfea_f21efa_b_26

Compare Source

🚀 New features and improvements
📦 Dependency updates

v1369.v15da_00283f06

Compare Source

🐛 Bug fixes

v1368.v066f524494ee

Compare Source

🐛 Bug fixes

v1367.v9ea_a_13875e39

Compare Source

🐛 Bug fixes

v1366.v23fd7b_ec4a_74

Compare Source

🐛 Bug fixes
  • Handle hash as well as query parameters in failure summary (#​751) @​timja
📦 Dependency updates

v1363.v2ea_b_461a_1480

Compare Source

🚀 New features and improvements
🐛 Bug fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added dependencies Pull requests that update a dependency file skip-changelog Should not be shown in the changelog labels Nov 23, 2025
Copy link

@A1exKH A1exKH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@renovate renovate bot force-pushed the renovate/org.jenkins-ci.plugins-junit-1380.x branch from 97433e4 to 6a428c4 Compare December 2, 2025 22:18
@renovate renovate bot force-pushed the renovate/org.jenkins-ci.plugins-junit-1380.x branch from 6a428c4 to 5ca5013 Compare December 12, 2025 23:11
@renovate renovate bot force-pushed the renovate/org.jenkins-ci.plugins-junit-1380.x branch from 5ca5013 to 24255e4 Compare December 13, 2025 04:13
Since we are including other plugins that are dependencies of junit, it
seems correct to include this plugin that is also a dependency of junit.

Testing done:

* Confirmed that tests pass that were failing prior to this change

Testing to do:

* Plugin BOM
* Acceptance test harness
@renovate
Copy link
Contributor Author

renovate bot commented Dec 13, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@MarkEWaite MarkEWaite self-assigned this Dec 13, 2025
Copy link
Contributor

@MarkEWaite MarkEWaite left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional tests passed in plugin BOM and in acceptance test harness.

@MarkEWaite
Copy link
Contributor

@jglick or @jtnord are there other things that should be evaluated before including this latest release of the JUnit plugin in Jenkins core? This update requires the addition of prism-api to Jenkins core.

@jtnord
Copy link
Member

jtnord commented Dec 15, 2025

@jglick or @jtnord are there other things that should be evaluated before including this latest release of the JUnit plugin in Jenkins core? This update requires the addition of prism-api to Jenkins core.

unless you want to requestion the decision of bumping detached plugins when there is a new release as opposed to a security release - the decision is just that, there is an update so it should be merged so long as all tests pass (are there any?). There was no quality metric in the original decision, nor anything about the ATH or bom builds. (it would make sense to use the bom build to manage these and then only bump the bom but that can give you a chicken and egg for the weeklies)?

If there are issues in the decision to merge bump PRs then we should not have them in the context of a single PR - it should be in the context of is this even right, or what else needs to be done to make it safe (if it is not safe). So no there is nothing from me.

FTR, CloudBees routinely strips all detached plugins and replaces them with ones of known good quality (including running the ATHs and PCTs).

@jglick
Copy link
Member

jglick commented Dec 15, 2025

Same: I do not really agree with the policy of routinely updating detached plugins—I rather think we should be removing detached plugins when the split point is more than a year or two old. But this has no effect on CloudBees CI and I do not have strong feelings either way, and yes any real policy discussion should happen on the list rather than in PR comments.

@MarkEWaite MarkEWaite self-requested a review December 15, 2025 18:28
Copy link
Contributor

@MarkEWaite MarkEWaite left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is now ready for merge. We will merge it after approximately 24 hours if there is no negative feedback.

/label ready-for-merge

@comment-ops-bot comment-ops-bot bot added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Dec 15, 2025
@MarkEWaite MarkEWaite merged commit 1bb6359 into master Dec 17, 2025
19 checks passed
@MarkEWaite MarkEWaite deleted the renovate/org.jenkins-ci.plugins-junit-1380.x branch December 17, 2025 03:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback skip-changelog Should not be shown in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants