-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jobs are stuck after a restart #350
Comments
This might help: https://plugins.jenkins.io/purge-build-queue-plugin/ |
Yep, but we would still need to do it manually. Would be nice to allow this action only for project leads. @mbarbero wdyt about a groovy init script that clears the queue after every Jenkins start? For reference: https://www.jenkins.io/doc/book/managing/groovy-hook-scripts/ |
agreed.
it depends :) Do we have cases where a Jenkins restart actually leads to successful jobs restart? If that's the case, then it means that by implementing your plan, you will effectively solve your issue, but also remove the auto-restart feature for others. |
I don't have hard numbers, but anecdotally it's rare that jobs in the queue start cleanly after a restart. |
+1 groovy init script If it don't work as expected, install `purge-build-queue-plugin for project. |
On https://ci.eclipse.org/sirius, I observed that some jobs have dissapered (without any information, as if they never existed). For example, a job sirius.sonar-master has been launched this morning. But it never ended and it is no longer visible. Is there a link with this issue ? |
Please open a separate HelpDesk issue about this. |
This is a recurring issue where the jenkins build queue is stuck after a reboot.
Workaround: clear the queue with
Jenkins.instance.queue.clear()
Related to https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4306#note_1754550
The text was updated successfully, but these errors were encountered: