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.

Sign up for GitHub

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

Jump to bottom

Simulate gitlab-runner heartbeats #20

Open
upsj opened this issue Dec 1, 2024 · 0 comments
Open

Simulate gitlab-runner heartbeats #20

upsj opened this issue Dec 1, 2024 · 0 comments

Comments

@upsj
Copy link
Member

upsj commented Dec 1, 2024

Currently when there are no jobs available, the runners are marked as stuck because they don't communicate with the GitLab API unless a job gets launched. If there is some kind of heartbeat/registration function available for runners in the undocumented API, we should use it to mark the runners as available.

With this change, a stuck runner would mark a serious problem instead of just a longer time since any jobs were executed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@upsj