[JIRA] (JENKINS-11225) Add aggregation and subview for multi-configuration projects
[ https://issues.jenkins-ci.org/browse/JENKINS-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163743#comment-163743 ] bnovc commented on JENKINS-11225: - I must have overlooked something before when trying to see individual configuration graphs. This seems to already work as I was describing. Perhaps I had looked at a configuration with no successes, so it didn't put up a graph. Add aggregation and subview for multi-configuration projects Key: JENKINS-11225 URL: https://issues.jenkins-ci.org/browse/JENKINS-11225 Project: Jenkins Issue Type: Improvement Components: warnings Affects Versions: current Reporter: Jonas Oscarsson Assignee: Ulli Hafner Issue added as a result of discussion from https://issues.jenkins-ci.org/browse/JENKINS-6772. In multi-configuration projects it would be preferable to have the warnings plugin show a different view for each matrix element. On the main page for the multi-configuration project we could have a aggregated view, showing the number of warnings for each matrix element. One specific case would be when having different compiler versions on one axis, and operating systems on the other. It would then be interesting to see warnings for the compiler gcc 4.4.2 compiling the project on RHEL4, as well as the warnings for gcc 4.6.1 compiling the project on RHEL5. The aggregated view would then show number of warnings for gcc 4.4.2/RHEL4 and gcc 4.6.1/RHEL5 on the main page, and the subviews would show the actual warnings for each combination of gcc and OS on the subpage. Let me know if I need to clarify further. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11225) Add aggregation and subview for multi-configuration projects
[ https://issues.jenkins-ci.org/browse/JENKINS-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163552#comment-163552 ] bnovc commented on JENKINS-11225: - I would be happy if the normal warnings plugin output was visible for each configuration when you click on them. In my case I don't care about getting any aggregation/totals, because there are going to be a lot of duplicates. Add aggregation and subview for multi-configuration projects Key: JENKINS-11225 URL: https://issues.jenkins-ci.org/browse/JENKINS-11225 Project: Jenkins Issue Type: Improvement Components: warnings Affects Versions: current Reporter: Jonas Oscarsson Assignee: Ulli Hafner Issue added as a result of discussion from https://issues.jenkins-ci.org/browse/JENKINS-6772. In multi-configuration projects it would be preferable to have the warnings plugin show a different view for each matrix element. On the main page for the multi-configuration project we could have a aggregated view, showing the number of warnings for each matrix element. One specific case would be when having different compiler versions on one axis, and operating systems on the other. It would then be interesting to see warnings for the compiler gcc 4.4.2 compiling the project on RHEL4, as well as the warnings for gcc 4.6.1 compiling the project on RHEL5. The aggregated view would then show number of warnings for gcc 4.4.2/RHEL4 and gcc 4.6.1/RHEL5 on the main page, and the subviews would show the actual warnings for each combination of gcc and OS on the subpage. Let me know if I need to clarify further. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14030) renaming a job does not preserve history
bnovc created JENKINS-14030: --- Summary: renaming a job does not preserve history Key: JENKINS-14030 URL: https://issues.jenkins-ci.org/browse/JENKINS-14030 Project: Jenkins Issue Type: Bug Components: core Reporter: bnovc When you rename a job, the history on the job is lost. I don't see any reason why this should happen and should at least be a choice. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11225) Add aggregation and subview for multi-configuration projects
[ https://issues.jenkins-ci.org/browse/JENKINS-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163197#comment-163197 ] bnovc commented on JENKINS-11225: - Seems like this has been open a while. Any chance this will come soon? Add aggregation and subview for multi-configuration projects Key: JENKINS-11225 URL: https://issues.jenkins-ci.org/browse/JENKINS-11225 Project: Jenkins Issue Type: Improvement Components: warnings Affects Versions: current Reporter: Jonas Oscarsson Assignee: Ulli Hafner Issue added as a result of discussion from https://issues.jenkins-ci.org/browse/JENKINS-6772. In multi-configuration projects it would be preferable to have the warnings plugin show a different view for each matrix element. On the main page for the multi-configuration project we could have a aggregated view, showing the number of warnings for each matrix element. One specific case would be when having different compiler versions on one axis, and operating systems on the other. It would then be interesting to see warnings for the compiler gcc 4.4.2 compiling the project on RHEL4, as well as the warnings for gcc 4.6.1 compiling the project on RHEL5. The aggregated view would then show number of warnings for gcc 4.4.2/RHEL4 and gcc 4.6.1/RHEL5 on the main page, and the subviews would show the actual warnings for each combination of gcc and OS on the subpage. Let me know if I need to clarify further. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs
[
https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162893#comment-162893
]
bnovc commented on JENKINS-12972:
-
{{git blame}} would be faster, but you would often not get correct results.
This only works if the problem you're trying to detect was caused by the last
edit to the line the problem was exposed.
I would really like to see {{git bisect}} offered as part of a normal build
with the git plugin. That way I would immediately know who broke the build
definitively. This would save significant time in triaging, as the person
responsible could be notified automatically.
Add option to run 'git bisect' to find which commit added new bugs
---
Key: JENKINS-12972
URL: https://issues.jenkins-ci.org/browse/JENKINS-12972
Project: Jenkins
Issue Type: New Feature
Components: analysis-core, core, findbugs, git
Reporter: Eyal Edri
Priority: Minor
Today, when you run find-bugs plug-in triggered by a git commit, you can't
know exactly which commit added those bugs.
It becomes especially difficult to know when a high volume of commits is
pushed at once.
find-bugs plug-in could have a new option to tick in the 'advanced section',
which will do a 'git bisect' on the git commits that caused a new bug and
display/email to commiter who did it.
that would simply and automate the process of finding who wrote the bug.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
