On Mon, Jun 25, 2012 at 5:21 PM, Bopolissimus X Platypus
wrote:
> When a job running on the slave is aborted (either at the browser via
> jenkins job control UI) or by the build timeout plugin, some commands
> started by batch files don't exit (they keep running).
this bug report:
https://issues
Hi All,
Is there a way to start slave.jar so that it will process just one job
and then exit when the job ends (either via success, failure or user
abort)?
I am currently prototyping. slave.jar runs (with -jnlpUrl) on Windows
2003. slave.jar runs from the command line (that may change as I get
On Sat, Jun 23, 2012 at 11:03 PM, Sami Tikka wrote:
> Arnaud, I thought the Xcode plugin solved all the issues about keychain
> management? I tried to open up a discussion about it some time ago but I
> was assured there really is no problem if people just use the Xcode plugin.
>
All I'm not sur
did you open an issue in JIRA?
https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking
On 22.06.2012, at 06:22, Bikash B wrote:
> I hope following gets fixed sooner
>
> https://github.com/dblock/jenkins-ansicolor-plugin/issues/11
>
>
> B
>
> On Wednesday, June 6, 2012 8:55:44 AM UTC+5:45
