Just to be clear, the solution you proposed for connecting is not just for
handling the temporary offline case?
Do you also have a solution for *disconnecting a slave,* not just
temporarily taking it offline (I want to close the channel of communication
between master and slave)?
In the* reco
On Friday, October 17, 2014 11:09:04 AM UTC-7, pjl8...@gmail.com wrote:
>
> Hi
>
> I need to disconnect and reconnect nodes programmatically ( in groovy if
> possible)
> is there a way to do this?
>
> Thanks
> Peter
>
--
You received this message because you are subscribed to the Google Gro
On Friday, October 17, 2014 11:09:04 AM UTC-7, pjl8...@gmail.com wrote:
>
> Hi
>
> I need to disconnect and reconnect nodes programmatically ( in groovy if
> possible)
> is there a way to do this?
>
> Thanks
> Peter
>
--
You received this message because you are subscribed to the Google Gro
Thanks for the suggestion.. .but same result
On Wednesday, April 23, 2014 11:55:29 AM UTC-7, Marc MacIntyre wrote:
>
> I assume that you only end up defining one curClosure variable, since it
> never goes out of scope, and subsequent changes to it update the one
> version you've added to your bu
I need to run a number of parameterized jobs in a parallel fashion, and
decided to try a simple example I recall seeing.
/ Build Flow TestHarness
/
// construct and collect closures for LATER execution
buildClosures = []
for (int i=1; i<50; i+
