[JENKINS-71272] ensure proper confirmDelete jelly is used #157
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.
In several Jenkins instances when deleting a Matrix run or a run of an axis the page that asks for confirmation was the one from Jenkins core and not the one provided by Matrix project plugin.
The Matrix Project delivers its own confirmDelete.jelly and puts it under .../resources/hduson/model/Run. This is the same location as in core which might lead to the wrong one taken if it is found first in the classpath for whatever reason.
This solves the issue for the price of duplication of the confirmDelete file.
Tested manually on a local Jenkins that showed the issue without this fix.
JENKINS-71272
Testing done
Submitter checklist