Reduce runner stale timeout from 3 months to 7 days
What does this MR do and why?
This MR reduces runner stale timeout from 3 months to 7 days. This causes more runners to classify as stale, and to be cleaned up by the Ci::Runners::StaleGroupRunnersPruneCronWorker
Changelog: changed
Closes #466312 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
![]() |
![]() |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
n/a
Merge request reports
Activity
changed milestone to %17.1
added Category:Fleet Visibility devopsverify grouprunner sectionci labels
assigned to @pedropombeiro
added pipelinetier-1 label
- A deleted user
added backend label
2 Warnings This MR changes code in ee/
, but its Changelog commit is missing theEE: true
trailer. Consider adding it to your Changelog commits.There were no new or modified feature flag YAML files detected in this MR. If the changes here are already controlled under an existing feature flag, please add
the feature flagexists. Otherwise, if you think the changes here don't need
to be under a feature flag, please add the label feature flagskipped, and
add a short comment about why we skipped the feature flag.For guidance on when to use a feature flag, please see the documentation.
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/administration/instance_limits.md
(Link to current live version) -
doc/api/graphql/reference/index.md
(Link to current live version) -
doc/ci/runners/runners_scope.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
Reviewer roulette
Category Reviewer Maintainer backend @ibaum
(UTC-5, 7 hours behind author)
@wandering_person
(UTC+7, 5 hours ahead of author)
test for spec/features/*
@ibaum
(UTC-5, 7 hours behind author)
Maintainer review is optional for test for spec/features/*
~"Verify" Reviewer review is optional for ~"Verify" @drew
(UTC+0, 2 hours behind author)
Please check reviewer's status!
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerEdited by Ghost User-
removed backend pipelinetier-1 labels
added pipelinetier-1 label
added featureenhancement typefeature labels
removed typefeature label
removed featureenhancement label
- Resolved by Leaminn Ma
requested review from @aluthra2
- Resolved by 🤖 GitLab Bot 🤖
Proper labels assigned to this merge request. Please ignore me.
@pedropombeiro
- please see the following guidance and update this merge request.1 Error Please add typebug typefeature, or typemaintenance label to this merge request. Edited by 🤖 GitLab Bot 🤖
added 1 commit
- d5d11d25 - Reduce runner stale timeout from 3 months to 7 days
- A deleted user
added backend label
added 1 commit
- 64abee95 - Reduce runner stale timeout from 3 months to 7 days
added 1 commit
- df6b520a - Reduce runner stale timeout from 3 months to 7 days
- A deleted user
added documentation label