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

Static code analyse #633

Open
svennissel opened this issue May 1, 2022 · 1 comment
Open

Static code analyse #633

svennissel opened this issue May 1, 2022 · 1 comment
Labels
Administrative Documentation, Build, Additional Tests, Research...
Milestone

Comments

@svennissel
Copy link
Collaborator

  • research for a easy way to make static code analyse like findbugs
  • We have no central server or budget to buy one.
  • Create a initial ruleset
  • Documentation for a developer to start code analyse

optional:

  • code coverage analyse
@svennissel svennissel added the Administrative Documentation, Build, Additional Tests, Research... label May 1, 2022
@svennissel svennissel added this to the 1.5.0 milestone May 1, 2022
@nuessgens
Copy link

Did not dig deep in to it: But did you have a look on GitHub Actions?
As I understood correctly this can perform such CI process and we could execute some static code analysis during the maven build. (maybe with spotbugs-maven-plugin)
Furthermore build may fail on failed unit-test.

There is Travis CI, too but as I understood it's not free of charge for open-source-projects (only a free trial available)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Administrative Documentation, Build, Additional Tests, Research...
Projects
None yet
Development

No branches or pull requests

2 participants