Don't run the job on the machine you need to disconnect. Instead, run it 
somewhere else, and have the build script connect to the actual build/test 
machine using e.g. SSH and run the commands from there.

On 08.03.2014, at 13:08, EK <eyas.ko...@gmail.com> wrote:

> Hi ...
> 
> I need to run a job which might cause slave to disconnect from Jenkins server 
> for a while- currently if slave is disconnected job is immediately marked as 
> failed or aborted, is there a way to do this, I was thinking about something 
> like the follow:
> 1. send job to slave
> 2. go offline
> 3. run job
> 4. go online
> 5. report results ...
> 
> Best Regards
> EK
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to