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

Add code quality plugins to jenkins build #790

Closed
2 tasks done
abrokenjester opened this issue Mar 26, 2017 · 7 comments
Closed
2 tasks done

Add code quality plugins to jenkins build #790

abrokenjester opened this issue Mar 26, 2017 · 7 comments
Assignees
Labels
🔧 internal task a project workflow / setup task not directly impacting end users wontfix issue won't be fixed (close reason)

Comments

@abrokenjester
Copy link
Contributor

abrokenjester commented Mar 26, 2017

We should look into adding some code quality plugins (like FindBugs, PMD, and/or CheckStyle) to the Jenkins build. This will make it easier for contributors to understand where their contributions need to be updated and will help us produce overall better code.

  • CQ22184: Spotbugs 4.0.3
  • CQ22185: Spotbugs maven plugin 4.0.0
@abrokenjester abrokenjester self-assigned this Mar 26, 2017
abrokenjester added a commit that referenced this issue Apr 1, 2017
@barthanssens
Copy link
Contributor

FWIW, I've started using Netbeans Inspect and Transform.
When enabling all the bells and whistles, there are a few thousands suggestions in the report, although most of them can be either ignored (e.g. using static imports, that's a matter of taste IMHO, I prefer not to use static imports) or are easy to "fix" (missing override annotation or javadoc param etc...)

@abrokenjester abrokenjester changed the title Add code quality plugins to travis build Add code quality plugins to jenkins build Oct 10, 2018
@barthanssens
Copy link
Contributor

Jenkins FindBugs is EOL, replaced by Warnings plugin https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin

@barthanssens
Copy link
Contributor

On a related note, there is also SpotBugs, available as Eclipse and maven plugin https://spotbugs.readthedocs.io/en/latest/maven.html

@barthanssens
Copy link
Contributor

FWIW, I'm currently looking into spotbugs, looks promising:

@barthanssens barthanssens added the ✋ CQ-Pending requires a CQ to be approved label Jan 7, 2020
@barthanssens
Copy link
Contributor

barthanssens commented Jan 7, 2020

  • CQ 21366 (PB) in IpZilla

@barthanssens barthanssens removed the ✋ CQ-Pending requires a CQ to be approved label Jan 15, 2020
@abrokenjester abrokenjester linked a pull request May 7, 2020 that will close this issue
@abrokenjester abrokenjester added the 🔧 internal task a project workflow / setup task not directly impacting end users label May 7, 2020
@barthanssens barthanssens added the ✋ CQ-Pending requires a CQ to be approved label May 14, 2020
@barthanssens
Copy link
Contributor

Creating a new one for more recent spotbugs version + plugins

barthanssens added a commit to Fedict/rdf4j that referenced this issue May 14, 2020
Signed-off-by:Bart Hanssens <bart.hanssens@bosa.fgov.be>
barthanssens added a commit to Fedict/rdf4j that referenced this issue May 14, 2020
Signed-off-by:Bart Hanssens <bart.hanssens@bosa.fgov.be>
@barthanssens barthanssens removed the ✋ CQ-Pending requires a CQ to be approved label Jun 15, 2020
@abrokenjester abrokenjester added the wontfix issue won't be fixed (close reason) label Jul 25, 2020
@abrokenjester
Copy link
Contributor Author

I closed this because the associated PR was closed - I get the feeling there was little enthusiasm for the idea in the end. Feel free to correct me and reopen though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔧 internal task a project workflow / setup task not directly impacting end users wontfix issue won't be fixed (close reason)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants