On Fri, May 25, 2018 at 11:48 AM, Matt Sicker wrote:
> try {
> Thread.sleep(...);
> } catch (InterruptedException ex) {
> Thread.currentThread().interrupt();
> }
If you receive an `InterruptedException`, I think you would rather
want to just abort the loop. Just be
I was concerned that calling Thread.currentThread().interrupt(); to not
cause any issues with Jenkins, like crash the job or something like that.
It's clear that it will stop the job, as it should. Just that it was not
clear to me how Jenkins handles this and if me doing this won't break
try {
Thread.sleep(...);
} catch (InterruptedException ex) {
Thread.currentThread().interrupt();
}
That's the normal Java idiom at least. The InterruptedException is checked
purely so you are forced to deal with it like this because it's the safer
way of killing a thread.
On Fri, May 25,
Hi,
I have a plugin that calls a MasterToSlaveCallable with the following
signature "private static class DataImportCallable extends
MasterToSlaveCallable".
Inside this MasterToSlaveCallable I zip some files and then upload them to
a server using Apache HTTPClient and then
On Fri, May 18, 2018 at 12:12 AM, Penugonda chenna reddy
wrote:
> I have downloaded the source code for the stapler-core example from github
I am afraid the people who work actively on Stapler use it exclusively
from the context of Jenkins and so it would hardly be
On Thu, May 24, 2018 at 5:53 PM, Slide wrote:
> You probably want to implement SimpleBuildStep in your Builder and then
> override the perform method that takes a Run and FilePath instead of a build
> object.
Yes. If the developer guide is not sufficiently clear about
Thank you. I'm a little busy over this weekend but will start on these as
soon as I can and get this plugin moving along again.
I'll take a look at PR45 too :)
On Friday, 25 May 2018 00:31:20 UTC+1, Oleg Nenashev wrote:
>
> Done. You should have access to GitHub now (if no, check your inbox for