Hi everyone,
we started the first activities in Jira [1].
We have set up an OFBiz build on our Jenkins server who automatically
does a FindBugs code analysis after each commit
I'm thinking about publishing the results on a web server. This should
help to engage contributors to work on the
Le 07/07/2017 à 15:12, Michael Brohl a écrit :
Avoiding duplicate errors should be managed through Jira. If someone wants to work on a class or package, he should file a Jira first so that
everyone can see that this is being worked on.
Agreed, having one wiki page as reference could also help
Avoiding duplicate errors should be managed through Jira. If someone
wants to work on a class or package, he should file a Jira first so that
everyone can see that this is being worked on.
The Jenkins FindBugs plugin/publisher has a very good output with
different filters and bug
Fantastic initiative Michael, +1
I think a simple attachment in jira or a wiki page will suffice. A
one-time scan would provide more than enough information for everyone
who needs to work on stuff. We can run it again in the future when
enough bugs have been tackled.
On Fri, Jul 7, 2017 at 1:43
I agree with Michael at OFBIZ-9450 that having "the results available to the public so that the community can always access the latest bug
statistics." should reduce duplicated efforts.
If we can produce the report in HTML format, then we can create a page in wiki and include the report in