That's the kind of feedback I need, thanks. I'm exploring right now and I don't yet have a feel for what's best practice, what's a terrible hack, and what's superfluous.
On Fri, Jun 13, 2014 at 4:17 PM, Mark Waite <[email protected]> wrote: > I've taken the simple minded approach of accepting that my > multi-configuration job (compiling and running tests on all nodes) test > results are separate from my test results for the single node "smoke test" > which precedes it. > > The description in the stackoverflow article sounded very complicated, > when all it does is save you the time of navigating two different jobs, the > upstream and the downstream. Wouldn't it be simpler to admit they are > different jobs with different responsibilities, and allow each of the jobs > to show only their own results? > > Mark Waite > > > On Fri, Jun 13, 2014 at 1:54 PM, Jamie Jackson <[email protected]> > wrote: > >> Hi All, >> >> Say I've got a project, A, which triggers a downstream job, B, which runs >> unit tests on all nodes of a cluster (using the "All Nodes for Label >> Factory" ParameterFactory option). My current triggering works fine, but >> I'd like to see all the test results in A's status. >> >> I'm new to all of this, and I'm pretty confused as to how to set this >> piece up. I've been searching, but it's tough to figure out all the >> fingerprinting (if that's even required) and/or aggregation of downstream >> jobs (if that's required), if you haven't done it before. >> >> These two articles seemed to do the most thorough job of explaining the >> process, but they seem to take some Jenkins knowledge for granted, and they >> gloss over them: >> >> - >> >> http://stackoverflow.com/questions/11051235/workaround-aggregate-downstream-test-results >> - >> >> http://shotgunsandpenguins.blogspot.com/2009/07/how-to-aggregate-downstream-test.html >> >> Could you help me figure out how how to get this set up? >> >> Thanks, >> Jamie >> >> -- >> 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. >> > > > > -- > Thanks! > Mark Waite > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/U08_YHLosgA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [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.
