Last time I looked at the code jobs run from the build flow don’t actually show up as downstream jobs – so the report aggregation is working flawlessly and aggregating all downstream jobs (which is no jobs).
So it’s not a configuration issue – but a code issue. Regards, /James From: [email protected] [mailto:[email protected]] On Behalf Of Thilo-Alexander Ginkel Sent: 22 October 2014 18:20 To: [email protected] Subject: build-flow test result aggregation not working Hi there, I have defined a parallel build using the build-flow plugin [1]: -- 8< -- revision = build.properties["environment"]["GIT_COMMIT"] parallel ( { build("rspec", GIT_COMMIT: revision) }, { build("cucumber-backend", GIT_COMMIT: revision) } ) -- 8< -- Both dependent build generate test results in JUnit format located in tmp/test_results/*.xml and have the "Publish JUnit test result report" post-build action pointed to that location. Fingerprinting is also enabled for tmp/test_results/*.xml. Both sub-builds display the test results correctly. What I can't seem to get working, though, is aggregating these results in the build-flow build, which has fingerprinting for **/* enabled and "Aggregate downstream test results" configured. Still, the build-flow build consistently states: "Latest Aggregated Test Result<https://jenkins.united-signals.com/job/build-flow/lastCompletedBuild/aggregatedTestReport/> (no tests)" Any ideas? Thanks, Thilo -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
