-
Notifications
You must be signed in to change notification settings - Fork 38
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
Bump com.github.spotbugs:spotbugs-maven-plugin from 4.7.3.6 to 4.8.2.0 #510
Bump com.github.spotbugs:spotbugs-maven-plugin from 4.7.3.6 to 4.8.2.0 #510
Conversation
16820ae
to
1d47d6a
Compare
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.
Bumps [com.github.spotbugs:spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin) from 4.7.3.6 to 4.8.2.0. - [Release notes](https://github.com/spotbugs/spotbugs-maven-plugin/releases) - [Commits](spotbugs/spotbugs-maven-plugin@spotbugs-maven-plugin-4.7.3.6...spotbugs-maven-plugin-4.8.2.0) --- updated-dependencies: - dependency-name: com.github.spotbugs:spotbugs-maven-plugin dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
1d47d6a
to
ceae5f4
Compare
jenkinsci/pom#510 needs this change along with checks of the other repositories that use the Jenkins parent pom. jenkinsci/pom#501 (review) recommends that the new spotbugs issues be either suppressed or resolved in the upstream release of spotbugs. This change suppresses the new warning for primitive fields that are pu9blicly visible and the new warning for a few cases where a field could be made static. This change skips the warnings related to CT_CONSTRUCTOR_THROWS because they are not relevant to Jenkins. jenkinsci/plugin-pom#869 (comment) provides more details along with the discussion at spotbugs/spotbugs#2695
Draft, not intended to be merged Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Does not need to be merged because there is no additional suppression required.
Draft, not intended to be merged Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Does not need to be merged because there is no additional suppression required.
Draft, not intended to be merged Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Does not need to be merged because there is no additional suppression required.
Draft, not intended to be merged Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Does not need to be merged because there is no additional suppression required.
Draft, not intended to be merged Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Does not need to be merged because there is no additional suppression required.
Draft, not intended to be merged Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Does not need to be merged because there is no additional suppression required.
Draft, not intended to be merged Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Does not need to be merged because there is no additional suppression required.
Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Needs to be merged on or before the update of the parent pom that updates to use spotbugs 4.8.2.
Draft, not intended to be merged Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Does not need to be merged because there is no additional suppression required.
Draft, not intended to be merged Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Does not need to be merged because there is no additional suppression required.
Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803
Draft, not intended to be merged Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Does not need to be merged because there is no additional suppression required.
Draft, not intended to be merged Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Does not need to be merged because there is no additional suppression required.
I believe that this is blocked on the following pull requests to resolve new spotbugs warnings. This pull request can be merged and released once these pull requests are merged,:
|
The CT_CONSTRUCTOR_THROW bug pattern is related to libraries used with SecurityManager and does not apply to Jenkins; we do not expect untrusted code to be running inside the controller JVM, therefore we suppress it globally. jenkinsci/plugin-pom#869 (comment) has more details.
Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Needs to be merged on or before the update of the parent pom that updates to use spotbugs 4.8.2.
jenkinsci/pom#510 needs this change along with checks of the other repositories that use the Jenkins parent pom. jenkinsci/pom#501 (review) recommends that the new spotbugs issues be either suppressed or resolved in the upstream release of spotbugs. This change suppresses the new warning for primitive fields that are pu9blicly visible and the new warning for a few cases where a field could be made static. This change skips the warnings related to CT_CONSTRUCTOR_THROWS because they are not relevant to Jenkins. jenkinsci/plugin-pom#869 (comment) provides more details along with the discussion at spotbugs/spotbugs#2695
Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803 Needs to be merged on or before the update of the parent pom that updates to use spotbugs 4.8.2.
Prep for * jenkinsci/pom#510 Part of the checklist in: * jenkinsci/jenkins#8803
As far as I can tell, this is ready to merge. I've confirmed the repositories in the checklist are ready for this change. If I missed a repository that depends on this change, I'll happily submit the pull request(s) to repair things after this is merged. |
I see that you have been working with Jesse Glick on this set of changes in the corresponding |
Thanks. The process in this pull request was an attempt to identify and resolve the spotbugs issues before the change to the parent pom was merged and released. I'm not sure that I have the stamina for the same level of rigor with the plugin pom. I see two options. I'm interested in which of the two options is the better choice.
|
As to the approach to be followed in |
Removes cd91eea workaround that was added in jenkinsci#708 jenkinsci/pom#510 is the pull request to the parent pom. It was released in parent pom 1.109.
Bumps com.github.spotbugs:spotbugs-maven-plugin from 4.7.3.6 to 4.8.2.0.
Release notes
Sourced from com.github.spotbugs:spotbugs-maven-plugin's releases.
... (truncated)
Commits
4737e86
[maven-release-plugin] prepare release spotbugs-maven-plugin-4.8.2.06052ca1
[pom] Sort order of maven reporting api/impl4ed4adc
Merge pull request #687 from hazendaz/master8b483fc
[pom] Remove clean goal from invoker as its never existed7ef8b3a
Merge pull request #686 from hazendaz/master2f28d9c
[GHA] For maven wrapper downloads, just use maven there to do that instead of...c0b13b8
Merge pull request #684 from spotbugs/renovate/maven-3.x1df4aad
Merge pull request #685 from spotbugs/renovate/mavenversiondb1181d
Update mavenVersion to v3.9.622ff278
Update dependency maven to v3.9.6You can trigger a rebase of this PR by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)