Repository navigation
ci: run SpotBugs through the foundry facade - #166
Merged
Merged
Conversation
v2.3.0 pins a setup-gradle SHA that doesn't exist (fixed in foundry#42), so the backend gate fails before it starts. main also has the spotbugs verb (foundry#36), so SpotBugs moves into the facade and quality.yml drops its own job.
CMaintz
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Foundry v2.4.0 is out and
@v2now points at it, with the setup-gradle fix (foundry#42) and themise run spotbugsverb (foundry#36). So the gate stays on@v2, and this just picks up the SpotBugs part.spotbugs: trueon the backend facade call; backend/mise.toml already had thespotbugstask for itBackend gate / java / SpotBugsnow