-
Improvement
-
Resolution: Fixed
-
Minor
-
None
Currently it isn't possible to see which configurations of a multi-configuration project cause which compiler warnings. At the root level only a list of all warnings are shown. And one needs to look at the individual configuration to see which warning is produced by which configuration.
This information could be presented multiple ways including:
- show the configuration name as extra information (for "Folder", "Files" and "Warnings" tabs it could be its own column. For details it should be added to the header)
- add a new tab "Configuration". It works like "Details" but the warnings are grouped by configurations
- have the whole table with the tabs shown once per configuration
[JENKINS-26913] Add more information about warnings for multi-configuration projects
As a first workaround I appended the configuration name to the module name. Is the module name normally used in your use case or is it empty? I'm not sure if it is worth the effort to create a new tab or if the existing module tab can be reused here. (As the package tab is used for folders if the project does not support packages). What do you think? Is this already enough? You can grab the latest build from our CI server, see wiki link.
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_core/AnalysisAction.java
src/test/java/plugins/WarningsPluginTest.java
http://jenkins-ci.org/commit/acceptance-test-harness/b5f5397361f77b7dd487a438eb7eb2264546234d
Log:
JENKINS-26913 Added test case that verifies the tab contents of a matrix build.
Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/178e8f82c2c6...b5f5397361f7
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/java/hudson/plugins/warnings/WarningsAnnotationsAggregator.java
http://jenkins-ci.org/commit/warnings-plugin/214ad4fbd7e42b5b74ac415fc31345a3f5a777d5
Log:
JENKINS-26913Append the configuration name to the module name when aggregating the warnings of a matrix build.