Am Dienstag, 18. Dezember 2018, 21:04:02 CET schrieb Jesse Glick: > On Mon, Dec 17, 2018 at 3:48 PM Martin Weber <[email protected]> wrote: > > in my plugin, do I have to always call > > hudson.Launcher.ProcStarter.stderr(OutputStream)? > > No, you should not. The call to `stdout(TaskListener)` ought to suffice.
OK. > > > The docs say I do not have to; if unset, stderr output would go to stdin. > > stdout I suppose you mean? Of course, sorry. > > > But > > I could not find any code in jenkins-core that is handling that case. > > https://github.com/jenkinsci/jenkins/blob/b826edb23de393bf1d79227247594b533a > d7b363/core/src/main/java/hudson/Proc.java#L224 Thank you. So I think it is unlikely for the missing build log lines [1] to be caused by my plugin. Should I push the issue to pipeline component? Martin [1] https://issues.jenkins-ci.org/browse/JENKINS-55215 -- E-Mails sollten Text sein, Text und nur Text. Wenn Gott gewollt hätte, dass E-Mails in HTML geschrieben würden, endeten Gebete traditionell mit </amen>. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/140479457.vrZoTEL6AM%40linux. For more options, visit https://groups.google.com/d/optout.
