I don't think blocking slave/agent for long duration is a good idea, except
if a single test can be run at once for a particular platform. Thus, you
must consider the hosting platform as a jenkins slave/agent and use a
waiter script.
If you need feed back managed by Jenkins, may be you can use
I think our longest test is 20 hours. Also, any number of tests can be spooled
at a particular time.
The legacy system just puts the job in the queue and returns.
Jeff
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this
@googlegroups.com
Subject: RE: Suggestions needed
How long does the hardware testing take? If its only a couple of hours, why
not just run a shell step to ssh or whatever out to the hardware and test? A
shell step normally blocks until completed, so the job will be in-progress
until the tests are
How long does the hardware testing take? If its only a couple of hours, why
not just run a shell step to ssh or whatever out to the hardware and test? A
shell step normally blocks until completed, so the job will be in-progress
until the tests are done.
-Original Message-
From: jenkin
