This seems too be happening only wen I run Jenkins in a Master/Slave setup (2 servers). If I only have the master it seems there's no problem with the output.
I'll try to see if I can setup 2.173 the same way (master + slave) to see if it's still reproducible. On Tuesday, April 16, 2019 at 4:02:48 PM UTC+3, Jesse Glick wrote: > > On Tue, Apr 16, 2019 at 5:16 AM Daniel Anechitoaie > <[email protected] <javascript:>> wrote: > > Any idea what's going on? > > Check whether it happens in Jenkins 2.173. If not, there is a backport > to LTS I could propose. If it still does, then I suspect something in > `git` or `git-client` will need to do a `flush()` somewhere. The code > here is nonstandard and problematic (JENKINS-21342) but nobody dares > touch it. Might suffice for `GitCommandMasterToSlaveCallable` to call > some new `GitClient.flush()` method defined on `CliGitAPIImpl`. If you > have a consistent way to reproduce this it would be helpful. > -- 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/8210af96-a327-4676-814b-97dc38eb4bdc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
