Blueoncean, split your script in  functions and  stages and you will get a 
good understanding of what is actually happening on every stage (clone, 
build, fail, etc). Also using groovy and try/catch will help too

On Friday, September 1, 2017 at 2:25:05 AM UTC+10, Dallas Clement wrote:
>
> I am working with multibranch pipeline builds and I want to be able to 
> tail the end of the console output to include in build failure email 
> notifications.  I can see where the log file is located in the filesystem 
> under 
>
> /var/lib/jenkins/jobs/<name of project>/branches/<name of branch>/builds/5
>
> The build log appears to have the console output embedded in it.  But 
> there appears to be a whole lot more also.  How can I extract / render just 
> the console output?
>
>
>

-- 
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/7b1748e9-46b7-4e4b-b4e0-7efedd065818%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to