Skip to content
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

Merged
merged 1 commit into from
May 5, 2023

Conversation

jglick
Copy link
Member

@jglick jglick commented May 3, 2023

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:

  • There are at least two (2) approvals for the pull request and no outstanding requests for change.
  • Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
  • Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
  • Proper changelog labels are set so that the changelog can be generated automatically.
  • If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
  • If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

@NotMyFault NotMyFault added the skip-changelog Should not be shown in the changelog label May 3, 2023
@NotMyFault NotMyFault requested a review from a team May 3, 2023 13:40
@NotMyFault
Copy link
Member

/label ready-for-merge


This PR is now ready for merge. We will merge it after ~24 hours if there is no negative feedback.
Please see the merge process documentation for more information about the merge process.
Thanks!

@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 May 4, 2023
@NotMyFault NotMyFault merged commit 15c0a94 into jenkinsci:master May 5, 2023
@jglick jglick deleted the ConfidentialStore.TEST branch May 5, 2023 16:29
Copy link
Member

@basil basil left a comment

Choose a reason for hiding this comment

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

@MarkEWaite
Copy link
Contributor

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

@jglick
Copy link
Member Author

jglick commented May 8, 2023

@MarkEWaite
Copy link
Contributor

https://github.com/jenkinsci/tfs-plugin/blob/aea4ce0f1fd82668b1ead7e2aade2ffe36a32a10/pom.xml#L15 is too old.

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?

@jglick
Copy link
Member Author

jglick commented May 9, 2023

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 ConfidentialStoreOverride and I guess also SecretOverride.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

5 participants