The code is pretty complex, and getting more complex, but to summarize the
steps in question are batch or shell scripts (depending on the platform)
which run a compilation (and later more that will run various tests). How
long they take can be quite variable, for example depending on whether a
I see - it's a bit tricky to understand how your setup works without
actually seeing the code you've written. Maybe you can look at the longest
build time and set that as the timeout if the agent execution is happening
inside the script rather than as a separate job
On Friday, 2 December 2016 1
Thanks, but I'm not sure this does what I need.
The impression I have is that the timeout step is based on how long the
contained step takes to execute.
What I need is a timeout based on when step actually does something. such
as generate some output.
A full build can take a long time, if I se
You can implement timeout following this guide - this one is for user input
but you can adapt it accordingly with a try/catch block.
https://support.cloudbees.com/hc/en-us/articles/226554067-Pipeline-How-to-add-an-input-step-with-timeout-that-continues-if-timeout-is-reached-using-a-default-value
It seems it was the windows slave specifically that was blocking things.
When I stopped the slave app the OSX slave kicked into action.
The questions above still apply.
On Thursday, December 1, 2016 at 1:39:33 PM UTC, Jonathan Hodgson wrote:
>
> Hi,
>
> Right now I'm looking at a pipelne job whi
Hi,
Right now I'm looking at a pipelne job which has been hung on two slaves
for over two hours.
Both slaves (one windows, one OSX) show as being connected, and the slave
is still running on both, but both are stalled... one on starting a batch
script, the other either in the shell script or j
