On Wed, Apr 17, 2019 at 3:53 PM Martin Weber wrote:
> Could this cause JENKINS-55215?
Unlikely. That is just using the normal
`ProcStarter.stdout(TaskListener)` which should not need any special
`flush` call, either before or after
https://github.com/jenkinsci/jenkins/pull/3961
--
You
Am Dienstag, 16. April 2019, 23:06:34 CEST schrieb Jesse Glick:
> On Tue, Apr 16, 2019 at 12:57 PM Daniel Anechitoaie
>
> wrote:
> > 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
On Tue, Apr 16, 2019 at 12:57 PM Daniel Anechitoaie
wrote:
> 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.
Yes, this is specific to use of Remoting.
--
You received this
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
On Tue, Apr 16, 2019 at 5:16 AM Daniel Anechitoaie
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
And if you look at the timestamp:
[2019-04-16T09:06:31.*541Z*] [Pipeline] myPlugin
[2019-04-16T09:06:31.208Z] Seen branch in repository origin/feature/pr1
[2019-04-16T09:06:31.208Z] Seen branch in repository origin/master
[2019-04-16T09:06:31.208Z] Seen 2 remote branches
the logs that appear
The strange thing is that this part of the log that appears under the other
stage:
---
[2019-04-16T09:06:31.211Z] > git show-ref --tags -d # timeout=10
[2019-04-16T09:06:31.224Z] > git config core.sparsecheckout # timeout=10
[2019-04-16T09:06:31.229Z] > git checkout -f
For some reason the console output seems to be all mixed. Like the output
from on step is present in other step.
Notice how "(BeginCheckRun)" stage started, yet the output from (Git) stage
is not finished, and part of the (Git) stage is also printed after
(BeginCheckRun) stage started.
Any idea
