Skip to content
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

Open
heurtematte opened this issue Feb 19, 2024 · 8 comments
Open

Jobs are stuck after a restart #350

heurtematte opened this issue Feb 19, 2024 · 8 comments

Comments

@heurtematte
Copy link
Contributor

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

@fredg02
Copy link
Contributor

fredg02 commented Feb 20, 2024

@mbarbero
Copy link
Member

@fredg02
Copy link
Contributor

fredg02 commented Feb 20, 2024

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/

@mbarbero
Copy link
Member

mbarbero commented Feb 20, 2024

Yep, but we would still need to do it manually. Would be nice to allow this action only for project leads.

agreed.

@mbarbero wdyt about a groovy init script that clears the queue after every Jenkins start?

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.

@fredg02
Copy link
Contributor

fredg02 commented Feb 20, 2024

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.

@heurtematte
Copy link
Contributor Author

+1 groovy init script

If it don't work as expected, install `purge-build-queue-plugin for project.

@lredor
Copy link

lredor commented Feb 21, 2024

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 ?

@fredg02
Copy link
Contributor

fredg02 commented Feb 21, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants