I see jobs failing with "FATAL: command execution failed" caused
by java.io.EOFException. I understand the connection to the remote node
drops, so java.io.EOFException is raised. Is it possible to re-run the job
remotely without failing it at all? I've seen the Naginator plugin, but it
seems
ce environment variables and other tokens.
>
> On Mon, May 13, 2019 at 8:50 AM Alexandru Băluț > wrote:
>
>> The jobs in my setup are triggered externally and the job gets as
>> parameter a commit SHA and at the end, depending on the result, a person
>> picked by
The jobs in my setup are triggered externally and the job gets as parameter
a commit SHA and at the end, depending on the result, a person picked by
the job should get an email.
I'm trying to use *Editable Email Notification* for this, but I'm not sure
how to make it work.
- In *Triggers* I
; 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 node. The shell script starts some j
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.
I set up job A which has a single *Trigger/call builds on other projects *build
step which *For every property file, invoke one build* of job B. The *File
Pattern* is /var/lib/jenkins/cases/*
Job B is started as expected, but the DATASET parameter is not passed
through even though it's
It seems the script is killed when the command-launcher plugin is done with
the agent. I filed https://issues.jenkins-ci.org/browse/JENKINS-50842
On Tuesday, 10 April 2018 15:40:57 UTC+2, Alexandru Băluț wrote:
>
>
>
> On 5 April 2018 at 15:44, Alexandru Băluț <alexandru.
On 5 April 2018 at 15:44, Alexandru Băluț <alexandru.ba...@gmail.com> wrote:
> I'm using Jenkins ver. 2.107.1 and I created a Node. See the screenshot
> below for the configuration details of the Node.
>
>
>
>
The problem I reported seems to be gone. But now there
I'm using Jenkins ver. 2.107.1 and I created a Node. See the screenshot
below for the configuration details of the Node.
The node is launched by a "Launch command" which starts an expensive cloud
instance, then starts the agent remotely through ssh, then after the agent
process stops shuts down
