But how do you guarantee that the second job runs on the same slave as the
first, unless you pin both jobs to a single slave?
On May 3, 2013 12:12 AM, Martin Ba 0xcdcdc...@gmx.at wrote:
On 03.05.2013 03:36, Eric Blom wrote:
Hello Everyone,
We started using Jenkins about a year ago and have
] On Behalf Of Paul Weiss
Sent: 03 May 2013 13:45
To: jenkinsci-users@googlegroups.com
Subject: Re: Execute Clean Up on Build Cancel
But how do you guarantee that the second job runs on the same slave as the
first, unless you pin both jobs to a single slave?
On May 3, 2013 12:12 AM, Martin Ba
On 03.05.2013 14:44, Paul Weiss wrote:
But how do you guarantee that the second job runs on the same slave as
the first, unless you pin both jobs to a single slave?
Wll - on first sight, no clue, really. :-)
Then, again, a short search yields:
Hello Everyone,
We started using Jenkins about a year ago and have been very happy with it. We
keep finding more way to use it! Some of our jobs use hardware connected to the
slave and when that slave job is canceled we need to execute a clean up step,
how can this be done?
I'm looking for a
On 13-05-02 09:36 PM, Eric Blom wrote:
trap /home/jenkins/tmp/cleanup.sh INT TERM
There is also the EXIT pseudo-signal available in bash.
On the command line I'm testing with Ctrl+C (INT). Based on the webpage below
I believe SIGTERM (TERM) should work for Jenkins' cancel button
Yes, an
On 03.05.2013 03:36, Eric Blom wrote:
Hello Everyone,
We started using Jenkins about a year ago and have been very happy with it. We
keep finding more way to use it! Some of our jobs use hardware connected to the
slave and when that slave job is canceled we need to execute a clean up step,
