-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deleting unused ConfidentialStore.TEST
#7925
Conversation
/label ready-for-merge This PR is now ready for merge. We will merge it after ~24 hours if there is no negative feedback. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the ci.jenkins.io job (sorry about that). The test results are also stored at https://github.com/jenkinsci/bom/pull/2051/checks?check_run_id=13318131478 |
I agree that the tfs plugin minimum Jenkins version is badly outdated. However, that plugin is suspended from distribution due to 3 open security vulnerabilities and no maintainer. Is the tfs plugin somehow related to this test in a way that I don't understand? |
Yes, https://github.com/jenkinsci/tfs-plugin/blob/aea4ce0f1fd82668b1ead7e2aade2ffe36a32a10/tfs/src/test/java/jenkins/security/ConfidentialStoreOverride.java#L42 would no longer work in new versions of Jenkins. One of the tasks involved in bringing it up to date, if anyone ever does, would be to delete |
Cleaning up a package-scoped field that apparently should have been deleted in #4603 but was merely deprecated.
Testing done
N/A
Proposed changelog entries
N/A
Proposed upgrade guidelines
N/A
Maintainer checklist
Before the changes are marked as
ready-for-merge
:upgrade-guide-needed
label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).lts-candidate
to be considered (see query).