[JIRA] (JENKINS-55137) No branch name in logs from parallel branches anymore?
Title: Message Title Simon Harrison commented on JENKINS-55137 Re: No branch name in logs from parallel branches anymore? Although this states "Resolved", we still have lost branch names from the logs after updating to version 2.80. This creates problems for us. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196204.1544601655000.9414.1584617040283%40Atlassian.JIRA.
[JIRA] (JENKINS-55137) No branch name in logs from parallel branches anymore?
Title: Message Title Shah Chowdhury commented on JENKINS-55137 Re: No branch name in logs from parallel branches anymore? We need the Branch Names in the Raw Logs. We have various tools/log-formatters that parse through raw logs. Please put this back. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196204.1544601655000.7704.1562806440251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55137) No branch name in logs from parallel branches anymore?
Title: Message Title Devin Nusbaum resolved as Duplicate See JENKINS-54304. Release 2.26 of Pipeline Job Plugin rewrote the log handling in Pipeline. Pipeline Job Plugin 2.31, which was released yesterday, displays branch labels in the console view of the classic UI, although there are still some quirks. If not having the branch names in the raw logs is a problem for you, please comment in that ticket so we understand the impact. Jenkins / JENKINS-55137 No branch name in logs from parallel branches anymore? Change By: Devin Nusbaum Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55137) No branch name in logs from parallel branches anymore?
Title: Message Title Evgeny Shepelyuk commented on JENKINS-55137 Re: No branch name in logs from parallel branches anymore? We experience exactly the same, not sure when it happen, but probably since last week update Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55137) No branch name in logs from parallel branches anymore?
Title: Message Title
Bertrand Roussel updated an issue
Jenkins / JENKINS-55137
No branch name in logs from parallel branches anymore?
Change By:
Bertrand Roussel
Before with parallel(), we used to have the branch name in the logs as a prefix for each log message from that branch.Now it seems that there is a mechanism to show/hide based on each branch.With the code:{code}builds = [:]builds['foo'] = { echo "message 1" }builds['bar'] = { echo "message 2" }parallel(builds){code}'Before':{noformat}[Pipeline] parallel[Pipeline] [foo] { (Branch: foo)[Pipeline] [bar] { (Branch: bar)[Pipeline] [foo] echo[foo] message 1[Pipeline] [foo] }[Pipeline] [bar] echo[bar] message 2[Pipeline] [bar] }[Pipeline] // parallel[Pipeline] End of PipelineFinished: SUCCESS{noformat}Now:{noformat} {noformat} [Pipeline] parallel[Pipeline] { (Branch: foo)[Pipeline] { (Branch: bar)[Pipeline] echomessage 1[Pipeline] }[Pipeline] echomessage 2[Pipeline] }[Pipeline] // parallel[Pipeline] End of PipelineFinished: SUCCESS {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55137) No branch name in logs from parallel branches anymore?
Title: Message Title
Bertrand Roussel created an issue
Jenkins / JENKINS-55137
No branch name in logs from parallel branches anymore?
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2018-12-12 08:00
Priority:
Major
Reporter:
Bertrand Roussel
Before with parallel(), we used to have the branch name in the logs as a prefix for each log message from that branch. Now it seems that there is a mechanism to show/hide based on each branch. With the code:
builds = [:]
builds['foo'] = { echo "message 1" }
builds['bar'] = { echo "message 2" }
parallel(builds)
'Before':
[Pipeline] parallel
[Pipeline] [foo] { (Branch: foo)
[Pipeline] [bar] { (Branch: bar)
[Pipeline] [foo] echo
[foo] message 1
[Pipeline] [foo] }
[Pipeline] [bar] echo
[bar] message 2
[Pipeline] [bar] }
[Pipeline] // parallel
[Pipeline] End of Pipeline
Finished: SUCCESS
Now:
[Pipeline] parallel [Pipeline] { (Branch: foo) [Pipeline] { (Branch: bar) [Pipeline] echo message 1 [Pipeline] } [Pipeline] echo message 2 [Pipeline] } [Pipeline] // parallel [Pipeline] End of Pipeline Finished: SUCCESS
