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 an additional job triggered using a project authentification token. Le jeudi 27 octobre 2016 15:59:12 UTC+2, Jeffrey Harris a écrit : > > 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 group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/74ce16cf-0797-4ffb-ad93-4a6ef37b4823%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
