-
New Feature
-
Resolution: Fixed
-
Minor
-
-
5.0.0-beta2
When splitting the different types of tests (integration test, performance test, statical analysis) in separated jobs from my main build job (compile / unit tests) in order to keep the build fast for the development team, I ran into the problem that reporting is scattered all around the different jobs.
Jenkins provides functionality to aggregate downstream test reports but I would also like to see that for other reporting.
- is related to
-
JENKINS-9739 Aggregation of downstream project reports for cobertura
-
- Open
-
[JENKINS-9066] Aggregation of downstream project reports for static analysis reports
Sietse Ten Hoeve
added a comment - Sorry for my late response but the answer is: yes. Every downstream project containing some reporting is performed with the intention to show it as part of the upstream job (I think this is true for almost all cases).
Sietse Ten Hoeve
added a comment - Sorry for my late response but the answer is: yes. Every downstream project containing some reporting is performed with the intention to show it as part of the upstream job (I think this is true for almost all cases). Please attach yourself as watchee on the new issue since I currently can't change the reporter.
Is there any workaround we can use until this is implemented?
Like archiving artifacts of the downstream projects and somehow collecting them in the upstream project?
I don't see a workaround. (And the implementation of that feature for tests seems to be not trivial.)
Carsten Otto
added a comment - Regarding the comment from 13/Sep/11 11:37 AM:
It is possible to archive the artifacts of the analysis itself (findbugs.xml generated by FindBugs) and then collect these artifacts in a job started from the upstream build. This involves, at least in my case, a python script and the "Join" plugin. Using this solution you can have different jobs for the analysis tools and a combined job for the analysis plugins (creating the graphs and such). However, I do not know how to have the tool run and the analysis of the results in one job and collecting all such results in another job.
Carsten Otto
added a comment - Regarding the comment from 13/Sep/11 11:37 AM:
It is possible to archive the artifacts of the analysis itself (findbugs.xml generated by FindBugs) and then collect these artifacts in a job started from the upstream build. This involves, at least in my case, a python script and the "Join" plugin. Using this solution you can have different jobs for the analysis tools and a combined job for the analysis plugins (creating the graphs and such). However, I do not know how to have the tool run and the analysis of the results in one job and collecting all such results in another job. 
I see. Should the aggregation use just all available downstream projects or just a sub set of them?