-
Bug
-
Resolution: Fixed
-
Major
-
None
-
-
Jenkins 2.136
When Launcher.ProcStarter.stdout(TaskListener) is called, this is merely an alias for stdout(OutputStream): getLogger() is called on the master side. Whereas the TaskListener passed to RemoteLauncher constructor and used for printCommandLine is properly remoted, that used for process stdout (and bundled stderr) is not.
When the implementation happened to be a StreamTaskListener, RemoteLauncher.launch winds up wrapping the stream in RemoteOutputStream, so content is still sent back to the master. But an implementation which does something else with the content on the remote side will not be honored.
- blocks
-
JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task
- Resolved
- relates to
-
JENKINS-31096 Unicode characters in console logs do not print correctly in Workflow builds
- Resolved
-
JENKINS-48923 Core should use UTF-8 by default
- Open
-
JENKINS-54073 "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
- Resolved
-
JENKINS-54929 Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
- Resolved
-
JENKINS-52914 Move AbstractBuild#createLauncher() logic to the Run Level
- Open
- links to