-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Windows 10
Jenkins 2.73.1
After Jenkins is restarted for any reason, ongoing jobs go into a stale state.
Job will try to resume, but get stuck displaying:
{{Resuming build at Mon Nov 27 17:25:51 IST 2017 after Jenkins restart }}
Ready to run at Mon Nov 27 17:26:00 IST 2017
Nothing further will happen.
The stage where this happens (python pytest) reads:
lock('server-gpu') {
bat '''
call activate py35
call conda env list
call python.exe -m pytest --junitxml=test_results_nightly.xml
'''
}
Not sure if this has to do with the lock. The job acquired the lock before the restart and after the restart, other jobs I start wait for the lock so it seems to have gotten it.
Any idea for a solution or workaround (which is not completely manual) would be appreciated.
[JENKINS-48245] Jobs do not resume after Jenkins restart
shachar ilan
created issue -
shachar ilan
made changes -
| Description |
Original:
After Jenkins is restarted for any reason, ongoing jobs go into a stale state. Job will try to resume, but get stuck displaying: {{Resuming build at Mon Nov 27 17:25:51 IST 2017 after Jenkins restart }} {{Ready to run at Mon Nov 27 17:26:00 IST 2017}} Nothing further will happen. The stage where this happens (python pytest) reads: {code:java} lock('server-gpu') { bat ''' call activate py35 call conda env list call python.exe -m pytest --junitxml=test_results_nightly.xml ''' }{code} Not sure if this has to do with the lock. The job acquired the lock before the restart and after the restart, other jobs I start wait for the lock so it seems to have gotten it. Any idea for a solution or workaround (which is not completely manual) would be appreciated. |
New:
After Jenkins is restarted for any reason, ongoing jobs go into a stale state. Job will try to resume, but get stuck displaying: \{\{Resuming build at Mon Nov 27 17:25:51 IST 2017 after Jenkins restart }} {{Ready to run at Mon Nov 27 17:26:00 IST 2017}} Nothing further will happen. The stage where this happens (python pytest) reads: {code:java} lock('server-gpu') { bat ''' call activate py35 call conda env list call python.exe -m pytest --junitxml=test_results_nightly.xml ''' }{code} Not sure if this has to do with the lock. The job acquired the lock before the restart and after the restart, other jobs I start wait for the lock so it seems to have gotten it. Any idea for a solution or workaround (which is not completely manual) would be appreciated. |
| Component/s | New: lockable-resources-plugin [ 18222 ] | |
| Component/s | Original: pipeline [ 21692 ] |