-
Bug
-
Resolution: Unresolved
-
Minor
-
Environment 1:
Jenkins ver. 2.222.3 on Windows 10.
Basic Steps 2.20
Job running on master
Environment 2:
Jenkins ver. 2.190.1 on Debian 9
Basic Steps 2.18
Job running on a Windows Slave connected with JNLP4
My pipeline has the following options:
options {
timestamps ()
timeout(activity: true, time: 30, unit: 'SECONDS')
}
And canceling the job occurs after 45 seconds:
22:12:00 Timeout set to expire after 30 sec without activity
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Reservation)
[Pipeline] script
[Pipeline] {
[Pipeline] input
22:12:00 Input requested
22:12:45 Cancelling nested steps due to timeout
This happens for every time I was set (SECONDS, MINUTES and HOURS) - and every time was extended by one and a half times.
But if I changed my pipeline options to:
options {
timestamps ()
timeout(activity: false, time: 30, unit: 'SECONDS')
}
Every things is ok (sample log):
21:36:24 Timeout set to expire in 30 sec
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Reservation)
[Pipeline] script
[Pipeline] {
[Pipeline] input
21:36:24 Input requested
21:36:54 Cancelling nested steps due to timeout
Timeout was called after exactly 30 seconds.
I tested this on two different Jenkins instances, and for both I have the same result, as I described above.
