Re: What I miss with Pipeline: Console output from each node

2016-06-04 Thread Baptiste Mathus 
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"  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
>>> ?
>>> 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  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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/387fe20e-2071-4ab3-a5f7-bc9bbd4f7d4a%40googlegroups.com
> 
> .
> 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/CANWgJS5NLTfjubzkuksF1eB_TZO3PFLU_gUmjfE5PV7teEtSug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: What I miss with Pipeline: Console output from each node

2016-06-02 Thread Sverre Moe 
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 
>> ?  
>> 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  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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/387fe20e-2071-4ab3-a5f7-bc9bbd4f7d4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What I miss with Pipeline: Console output from each node

2016-06-02 Thread Sverre Moe 
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 
> ?  
> 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  > 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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/84861f8d-5747-4d44-acf3-5ad54f981c2d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What I miss with Pipeline: Console output from each node

2016-06-01 Thread Andrew Bayer 
Yeah, we still need parallel execution split out in the visualization and
log view...

A.

On Wed, Jun 1, 2016 at 10:31 AM, Patrick Wolf  wrote:

> Yes, as Craig mentioned this is partly solved using Stage View but the log
> view should be much more informative and readable after
> https://issues.jenkins-ci.org/browse/JENKINS-26107 is finished.
>
> On Wed, Jun 1, 2016 at 10:12 AM, Craig Rodrigues 
> wrote:
>
>> Hi,
>>
>> Did you try using the 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  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 jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CAG%3DrPVdz_ESpCUWGUEAWrawa26oHw-oyRvice%2BTe-_v662503A%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
> Patrick Wolf
> Sr. Product Manager
> CloudBees
>
> --
> 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/CAGDV0P9Wo2AGwbpbyM79uf9Pk_PkwcKx9zRgfS%2BLiAt5QZ6CaQ%40mail.gmail.com
> 
> .
>
> 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/CAPbPdObMRuL5UfL7vzT0qHJsdyaMoz-gjPdfp-fk%2BRDRR075SA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: What I miss with Pipeline: Console output from each node

2016-06-01 Thread Patrick Wolf 
Yes, as Craig mentioned this is partly solved using Stage View but the log
view should be much more informative and readable after
https://issues.jenkins-ci.org/browse/JENKINS-26107 is finished.

On Wed, Jun 1, 2016 at 10:12 AM, Craig Rodrigues 
wrote:

> Hi,
>
> Did you try using the 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  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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAG%3DrPVdz_ESpCUWGUEAWrawa26oHw-oyRvice%2BTe-_v662503A%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Patrick Wolf
Sr. Product Manager
CloudBees

-- 
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/CAGDV0P9Wo2AGwbpbyM79uf9Pk_PkwcKx9zRgfS%2BLiAt5QZ6CaQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: What I miss with Pipeline: Console output from each node

2016-06-01 Thread Craig Rodrigues 
Hi,

Did you try using the 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  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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAG%3DrPVdz_ESpCUWGUEAWrawa26oHw-oyRvice%2BTe-_v662503A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

What I miss with Pipeline: Console output from each node

2016-06-01 Thread Sverre Moe 
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.

I really miss from Multi-configuration having separate Console Output for 
each node. With pipeline it is very difficult to read the output from a 
single node. At least the Console Output lines are prepended with the node 
name.

For the build stage I can show the output from each step in that stage, but 
it is impossible to know which steps for which node.
*Click on Build stage
*Click on Logs
+Shell script
+Shell script
+Shell script
+Shell script
+Shell script
+Restore files previous stashed
+Verify if file exists in workspace
+Print message
+Shell script
+Shell script
+Shell script
+Shell script
+Shell script
+Restore files previous stashed
+Print message
+Shell script
+Shell script
+Shell script
+General build step
+Shell script


-- 
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/b92e5ad4-b008-4046-8b52-ad7c25528971%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.