If you call a poorly configured cleartool command from a pipeline job, timeout is unable to end the job when the timer is done.
Steps to reproduce:
-Ensure you have a slave(will work on ssh linux slave but I assume others could be the same)
-Ensure the cleartool command line tool has been installed for use
-Ensure you can access that cleartool command from Jenkins
-Create a pipeline job
-Create a timeout of something like 2 minutes
Run something like /opt/rational/clearcase/bin/cleartool lsbl -fmt ""%Nd\n -stream $STREAM (lsbl: List baseline information per stream or component or by promotion level, fmt option to set the format, –str/eam stream-selector) this step will actually keep going indefinitely because it is a bad command since the format should be between the double quotes("$COMMAND")
-Observe that even after 2 minutes the build is still going
In order for the job to stop, both /abort and /kill have to be called.
Expected results:
I would normally expect that the timeout ends the job
Possible causes:
I think that cleartool is locking resources and not ending properly when asked to
EDIT:
This actually does not even need a badly configured command. Clearcase if told to timeout will never exit until it is done. So if your clear case command takes 30 seconds and you time it out at 15, it will show as taking 30 and never actually timing out. When it comes back it will then end the job because of a timeout call.