Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Jenkins 2.138.2
-
-
workflow-job 2.31
Description
This issue manifested itself since October 15th.
When a build is triggered and it runs on multiple slaves parallely, you normally get an output for each line corresponding to the variant its running. Since a Jenkins update on October 15th, this has not been the case. This is making it harder for us to debug the issues on the variants/slaves, as we don't know on which variant the issue is being manifested.
NOTE:
Although unrelated, this issue was manifested together with another bug which doesn't allow an anonymous user to view jobs, even if logged in as a non-admin. Only users with admin privileges are allowed to view the logs. That issue has been found on your backlog. https://issues.jenkins-ci.org/browse/JENKINS-54031
Attachments
Issue Links
- is duplicated by
-
JENKINS-55137 No branch name in logs from parallel branches anymore?
-
- Resolved
-
-
JENKINS-54763 Branch name disappear after plugin upgrade (>= 2.26)
-
- Resolved
-
-
JENKINS-55332 Parallel branch no longer prefixing log lines
-
- Closed
-
- relates to
-
JENKINS-38719 ConsoleAnnotatorFactory serves stale JavaScript and CSS when a plugin is upgraded/downgraded
-
- Resolved
-
-
JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task
-
- Resolved
-
-
JENKINS-56734 After upgrading jenkins from 2.60 to 2.150.3, we are seeing one alignment issue in the console log when we are running 2 stages parallelly in a pipeline job
-
- Open
-
-
JENKINS-60862 Truncated build logs do not show parallel branch names that began before the truncation point
-
- Resolved
-
-
JENKINS-56910 Can no longer search for branch names of parallel() branches
-
- Open
-
-
JENKINS-56913 Support for filtering all occurrences of all parallel() branches except one in the job log
-
- Open
-
- links to
Hey jglick,
the change done here has killed our complete option to forward the log data to an external instance! This is really a major change that should be undone! Who cares about the log to be shown within the UI if you operate Jenkins within a corporation where you have some hundert jenkins jobs - you simply don't scroll trough the jobs anymore - you have to have some external processing.
Before this change we where able to forward all logs to an external FileBeat, split the logs via Logstash and process it within ElasticSearch. With this change, we are limited to the Jenkins UI.
With this change, there is currently NO efficient way to forward the logs anymore! The only way is the logstash plugin - but here you have to adapt all jobs and don't have any global "forward everything" option anymore (if you rely on 100% pipeline jobs).
Please re-add the [pipeline step name] and also remove the binary encoded stuff (8mha:////) from the logs.