|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] (JENKINS-15037) Option to consider only stable builds when calculating new warnings
david.pars...@gmail.com (JIRA) Thu, 13 Sep 2012 03:18:54 -0700
- [JIRA] (JENKINS-15037) Option to consider ... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... david.pars...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... david.pars...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... david.pars...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... david.pars...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... david.pars...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... david.pars...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... david.pars...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... david.pars...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15037) Option to consider ... david.pars...@gmail.com (JIRA)
Hm.. What should happen when a project has different warning priorities and one of them increases and another decreases? Ideally when this new option would be enabled, I wouldn't want to decrease any reference warning count for any priority. Using a single build as reference build would however not allow this, and this might complicate things even further.
I think it's more clear to just use the stable build as a reference, and ignore the fact that deltas might get messed up as stated in my comment above.