I think the way aggregation was intended to work, a job would produce
some artifact, fingerprint the artifact, and trigger downstream builds
to do something with the artifact. The test results would be aggregated
by the upstream job which created the artifact. The fingerprint provides
the link between a particular artifact build and the tests run on that
artifact. You can give the main-aggregator job this pattern by having it
create a simple artifact such as a timestamp and archive and fingerprint
it, and have the downstream jobs retrieve the artifact.
Regards,
Eric
On 9/17/2015 11:02 AM, Gergely Brautigam wrote:
Hello guys.
I know this has been chewed upon many times, and I've read blogs after
posts after questions and answers and descriptions and every damn
thing I was able to find on the internetz, still, I can't get
aggregation to work.
I have a project main-aggregator who has 6-10 other jobs configured as
a downstream project which generate test results in junit test format.
Configuration is handled through Jenkins DSL, but I tried without it
as well, so that doesn't matter.
Jobs are configured to be downstream through this guy => Trigger /
call builds on other projects. This has a list of jobs to trigger.
After that, the Aggregate Downstream Test result is added as post
build task and enabled to Automatically Generate results ( I tried
defining them by name as well ).
Next, the downstream projects have fingerprinting setup like this =>
publishers{
archiveJunit("project/build/${taskName}-results/TEST*xml")
fingerprint("project/build/${taskName}-results/TEST*xml")
}
This all works. I see the fingerprinted xml files, awesomeness.
But on the main calling build Jenkins says this =>
Aggregated Test Result
Fingerprinting not enabled on this build. Test aggregation requires
fingerprinting.
Well, of course it's not enabled. How would it be? This job isn't
generating anything it should AGGREGATE. Or I'm missing a vital point
here... But If I understand correctly aggregation requires tracked
results which I'm tracking on the build which is creating the result.
But I can't fingerprint anything on a build which is not doing
anything else other than triggering these builds. There is no flag to
set that says enable fingerprint and that's it, unless I'm missing
something.
Could somebody please help me before I loose my mind over this?
Thank you very much!
Gergely.
--
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 jenkinsci-users+unsubscr...@googlegroups.com
<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/d3466540-cc52-4130-8b9c-7e1c885ef1c5%40googlegroups.com
<https://groups.google.com/d/msgid/jenkinsci-users/d3466540-cc52-4130-8b9c-7e1c885ef1c5%40googlegroups.com?utm_medium=email&utm_source=footer>.
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/55FAFA49.3070006%40cd-adapco.com.
For more options, visit https://groups.google.com/d/optout.
