As other have suggested, you should use run your tests upon a jenkins slave
node.  We have a similar problem to you and we do this:

Jenkins -> Test Driver -> System Under Test

Here, Jenkins communications directly with the Test Driver; the test driver
communicates with several 'Systems Under Test'.   Test Driver can
communicate with VMware or EC2 to reset VMs or provision complex EC2
setups.  Our Test Driver polls until all our nodes are on-line and ready to
be tested.

Hope this help.

Dominic

On Wed, May 16, 2012 at 9:59 PM, Romu <huru...@gmail.com> wrote:

> Hi,
>
> How to reboot a slave as part of a build?  I found that when the slave
> reboots Jenkins immediately considers the build as failsure.
>
> Any idea?
>
> Thanks
> Romu
>



-- 
Dominic Maraglia
QA Engineer
Puppet Labs

Reply via email to