Regenerate policies on a regular basis
Problem
If data fetched from https://about.gitlab.com/ changes generated policies get out of date and cause
For example: !2669 (merged)'s pipeline failed very late in the lifecycle and was only unblocked by !2671 (merged).
Proposed solution
- Run
.gitlab/ci/scripts/regeneration-check
in CI on a regular basis (dailyhourly) - Create an MR if changes are detected
- Assign maintainers for review
Considerations
Could we use:
- https://gitlab.com/gitlab-org/frontend/renovate-gitlab-bot OR
- Triage-ops/GitLab Triage itself
to perform this task?
Edited by Peter Leitzen