Details
-
New Feature
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Hudson 1.361 on Windows Server 2003
Relevant plug-ins: FindBugs 4.10, Static Analysis Utilities 1.9
Description
For multi-configuration projects, links to FindBugs results won't be added to the project page. There also are no links on the build pages (the one you reach by clicking a link in "Build history" on the project page) and the pages on the configuration.
The FindBugs results can however be found on the build pages for the configurations (can be reached by clicking on a build in "Build history", then on a configuration).
Since in my case the FindBugs results should be identical over all configurations, I expected to find a link on the main project page, as it works with other project types. At least I would have expected to find a link on the configuration pages, not only the configuration pages for specific builds.
Attachments
Activity
Well, since there wasn't another requirement and no response to comment 1 I decided to implement the easiest solution. How do you use multi-configuration projects? Do you get different results for different configurations?
Jonas Oscarsson
added a comment - Thank you for the quick feedback.
I see. I use multi-configuration projects for building using different compilers (gcc 4.1.2, gcc 4.4.2, gcc 4.6.1) and different unix versions (rhel4, rhel5, solaris, etc). The different compiler versions gives different warnings, so in my case it would be interesting to see the compiler warnings for each element in the build matrix (for example, on rhel4 using gcc 4.4.2). At the top level, perhaps an aggregated view would be best, just showing the number of warnings for each matrix element.
What do you think? Do other people use multi-configuration projects differently, or could this be a general case suiting many different configurations?
Jonas Oscarsson
added a comment - Thank you for the quick feedback.
I see. I use multi-configuration projects for building using different compilers (gcc 4.1.2, gcc 4.4.2, gcc 4.6.1) and different unix versions (rhel4, rhel5, solaris, etc). The different compiler versions gives different warnings, so in my case it would be interesting to see the compiler warnings for each element in the build matrix (for example, on rhel4 using gcc 4.4.2). At the top level, perhaps an aggregated view would be best, just showing the number of warnings for each matrix element.
What do you think? Do other people use multi-configuration projects differently, or could this be a general case suiting many different configurations? That makes sense (at least for the warnings plug-in). Can you please create a new feature request in our issue tracker where you can briefly describe your requirements for the aggregation and the single configuration results.
Jonas Oscarsson
added a comment - I added a issue here: https://issues.jenkins-ci.org/browse/JENKINS-11225. Let me know if I need to clarify further or change anything.
Thanks!
Jonas Oscarsson
added a comment - I added a issue here: https://issues.jenkins-ci.org/browse/JENKINS-11225 . Let me know if I need to clarify further or change anything.
Thanks! 
Hi there!
First of all, thanks for a great plugin!
I just tried the warnings plugin with a multi-configuration project, and I find it a bit strange that it only shows warning for the first configuration. Wouldn't it be better if it showed warnings for each configuration on each configuration's page, and perhaps an aggregated view on the main project page?
Or perhaps the idea was to get something working for multi-configuration projects at all as a first step, and deal with more advanced features later on?
Just curious, thanks for your time