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

Suppress warnings for spotbugs 4.8.3 #465

Merged
merged 1 commit into from
Jan 16, 2024
Merged

Suppress warnings for spotbugs 4.8.3 #465

merged 1 commit into from
Jan 16, 2024

Conversation

MarkEWaite
Copy link
Contributor

Suppress warnings for spotbugs 4.8.3

jenkinsci/plugin-pom#869 or a subsequent pull request that updates to 4.8.3 will need this change in the plugin to resolve new spotbugs warnings that will be reported by spotbugs 4.8.2 and later.

Plugin pom 4.77 is likely to include that new version of spotbugs.

Testing done

Confirmed that the spotbugs warnings are visible when using the 4.77-SNAPSHOT plugin pom before this change. With this change, the spotbugs warnings are no longer visible.

Submitter checklist

request that updates to 4.8.3 will need this change in the plugin to
resolve new spotbugs warnings that will be reported by spotbugs 4.8.2
and later.

Plugin pom 4.77 is likely to include that new version of spotbugs.

Confirmed that the spotbugs warnings are visible when using the
4.77-SNAPSHOT plugin pom before this change. With this change, the
spotbugs warnings are no longer visible.
@MarkEWaite MarkEWaite requested a review from a team as a code owner January 15, 2024 20:43
@MarkEWaite
Copy link
Contributor Author

Thanks @kuisathaverat . This does not require a new release of the plugin. It can be labeled chore or skip-changelog. I just don't want the plugin pom upgrade to be blocked by a spotbugs warning.

@kuisathaverat kuisathaverat merged commit b8050d6 into jenkinsci:main Jan 16, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants