jenkinsci / jenkinsci/lockable-resources-plugin

[JENKINS-48245] Jobs do not resume after Jenkins restart

Open
#899 1 comment 0 reactions 0 assignees View on GitHub
component:lockable-resources-plugin imported-jira-issue Need test priority:major resolution:unresolved Triage
Dominant language
Java
Stars
99
Forks
205
Avg merge
2d 13h
Merged PRs (30d)
8

Description

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.

 

---
Originally reported by shachar, imported from: Jobs do not resume after Jenkins restart


  • status: Open
  • priority: Major
  • component(s): lockable-resources-plugin
  • resolution: Unresolved
  • votes: 3
  • watchers: 5
  • imported: 20251217-081411

Raw content of original issue

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.

 

environment

```
Windows 10

Jenkins 2.73.1
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.