Re-reading the thread I'm wondering what the use case actually is. I understand the need to read the logs of a single execution branch/thread of the pipeline (when some parallel is in play) to debug/understand things. But that seems actually unrelated to which node the pipeline runs on. Le 2 juin 2016 10:46 AM, "Sverre Moe" <[email protected]> a écrit :
> The main Console Output prepends all lines with the node name > > [master-sles11-i686] + ./autogen.sh > [master-sles11-x86_64] + ./autogen.sh > > > This could be use to split out the main Console Output with one for each > node. > > When https://issues.jenkins-ci.org/browse/JENKINS-26107 is finished it > would make the Log in Stage View more readable with label so one could > distinguish between steps of "Shell script". However the list of steps > within one stage is not structured by which node it executed on. > > torsdag 2. juni 2016 09.17.04 UTC+2 skrev Sverre Moe følgende: >> >> I have installed Pipeline Stage View Plugin and already been using it. I >> get Stage view visualization in the project, but it doesn't visualize each >> parallel execution. All steps in parallel executions within one stage are >> all listed on that one single stage. >> >> It is not allowed to have stage within a parallel execution, as far as I >> know. I got an exception when I tried it. If it could be possible to define >> stage within parallel I could use a different stage name for each parallel >> execution node. >> stage 'Build-node1' >> stage 'Build-node2' >> >> onsdag 1. juni 2016 19.12.09 UTC+2 skrev Craig Rodrigues følgende: >>> >>> Hi, >>> >>> Did you try using the Pipeline Stage View Plugin >>> <https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin>? >>> It breaks the log down by stage quite nicely, such as in this example: >>> https://jenkins.freebsd.org/job/FreeBSD_HEAD/ >>> >>> I haven't tried it with pipelines that execute in parallel, so would be >>> curious as to how it works for you >>> >>> -- >>> Craig >>> >>> On Wed, Jun 1, 2016 at 3:07 AM, Sverre Moe <[email protected]> wrote: >>> >>> I have been using Jenkins Multi-configuration. With my move over to >>>> Pipeline scripts and Jenkinsfile I still build on multiple nodes/slaves. >>>> When building all the nodes in parallel the console output is a mess. >>>> It is very difficult to separate the output from a single node. >>>> >>>> -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/387fe20e-2071-4ab3-a5f7-bc9bbd4f7d4a%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/387fe20e-2071-4ab3-a5f7-bc9bbd4f7d4a%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS5NLTfjubzkuksF1eB_TZO3PFLU_gUmjfE5PV7teEtSug%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
