I see what you mean, but "exit 0" is executed and despite being executed
the job still fails. See the copy/pasted console log.
On Wednesday, May 8, 2019 at 2:37:01 AM UTC+2, ok999 wrote:
>
> If I remember correctly, the non 0 status of the command is enough to
> exit. Your exit 0, will not be
If I remember correctly, the non 0 status of the command is enough to exit.
Your exit 0, will not be executed. There is a workaround for that.
On Tue, May 7, 2019 at 3:28 PM Alexandru Băluț wrote:
> I set up a freestyle job which has a single "Execute shell" build step,
> and is run on a remote
I set up a freestyle job which has a single "Execute shell" build step, and
is run on a remote node. The shell script starts some jobs in the
background, then waits for one of them to exit, then kills them all with
"killall -9 jobName || echo dead", then at the end it "exit 0" to signal
success.
