[JIRA] (JENKINS-61383) Use information from git forensics to improve detection of new warnings

8 views
Skip to first unread message

ullrich.hafner@gmail.com (JIRA)

unread,
Mar 9, 2020, 3:43:03 AM3/9/20
to jenkinsc...@googlegroups.com
Ulli Hafner updated an issue
 
Jenkins / Improvement JENKINS-61383
Use information from git forensics to improve detection of new warnings
Change By: Ulli Hafner
Issue Type: Bug Improvement
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

ullrich.hafner@gmail.com (JIRA)

unread,
Mar 9, 2020, 3:43:03 AM3/9/20
to jenkinsc...@googlegroups.com
Ulli Hafner updated an issue
Change By: Ulli Hafner
Summary: warning-ng reports warning to be new based on false Use information from git forensics report to improve detection of new warnings

idooph@checkpoint.com (JIRA)

unread,
Mar 9, 2020, 4:25:02 AM3/9/20
to jenkinsc...@googlegroups.com
Why Name commented on Improvement JENKINS-61383
 
Re: Use information from git forensics to improve detection of new warnings

I saw you changed the issue to major Improvement. Well like the say it depends if you are a buyer or a seller...

From a User point of view it is definitely a bug and a critical one. Because the algorithm does not work in my case (and I have many more examples), therefore it is unreliable. the whole point to characterize a message as a new is that people can devote their energy to new messages (only). But when I mark old message as new one I lose the attention that people were willing to give to the static code analysis tool.

From a Developer point a view the algorithm is working only in most cases so it is a call for major improvement (or picking a different algorithm).  

I tend to think that Jira should serve mainly the "user prospective"  for bugs and "user & developer prospective" for improvements. But I this case I personally favor user prospective. 

Anyway, thanks for pointing out  the exact code, I will try to come with an offer for improvement hopefully soon.

 

 

 

ullrich.hafner@gmail.com (JIRA)

unread,
Mar 9, 2020, 4:57:02 AM3/9/20
to jenkinsc...@googlegroups.com

You can set the priority to the value you like. So if you feel that it needs to be a blocker, then go ahead. For me it does not really make any difference. Typically we use blocker in Jenkins for things that break a plugin. Like a NPE or a class loading problem during a release upgrade. These bugs I try to fix asap.

But in this case you still can use the plugin, just the number of new warnings is wrong. And this is something that we can't solve in general, we can just improve the heuristics.

idooph@checkpoint.com (JIRA)

unread,
Mar 9, 2020, 5:22:02 AM3/9/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages