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

Add support for setting check_interval #315

Merged
merged 1 commit into from
Mar 14, 2024

Conversation

fkleon
Copy link
Contributor

@fkleon fkleon commented Feb 19, 2024

Add support to set check_interval in the global config section.

check_interval: Defines the interval length, in seconds, between the runner checking for new jobs.
The default value is 3. If set to 0 or lower, the default value is used.

See https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-global-section

This defaults to 0 which matches the default auto-generated config, and simply causes GitLab runner to use its default value (see above). So this shouldn't cause any change in behaviour for existing users of this role.

@fkleon
Copy link
Contributor Author

fkleon commented Mar 13, 2024

@guenhter just wondering if you can have another look at this?

@guenhter guenhter merged commit 1a6e8d7 into riemers:master Mar 14, 2024
1 check failed
@guenhter
Copy link
Collaborator

@fkleon Thx for this contribution

maybe you can keep your eyes open for incoming issues which might be caused by a this change.

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

Successfully merging this pull request may close these issues.

None yet

2 participants