-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 2.138.2
-
-
workflow-job 2.31
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
- 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
[JENKINS-54304] Jobs in parallel dont display the variant they are running.
Description |
Original:
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. |
New:
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 |
Component/s | New: pipeline [ 21692 ] | |
Component/s | Original: _unsorted [ 19622 ] |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] | New: Jesse Glick [ jglick ] |
Component/s | New: workflow-job-plugin [ 21716 ] | |
Component/s | Original: pipeline [ 21692 ] |
Link |
New:
This issue relates to |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
jglick svanoort I believe it is just another issue caused by the recent Pipeline plugins. PTAL
fhajredini please provide the list of plugin versions you have installed on your instance