Increase the scope of triaged groups & projects and reorganize CI config and policy files
- Creates a new CI config to declare group and project specific jobs.
- Change the job-selection process to variables now that our pipeline schedules are automated and versioned, this method is very convenient and reduce the duplication a lot:
- No need for declaring
DAILY_AUTOMATION
/WEEKLY_AUTOMATION
,TRIAGE_SOURCE_TYPE
,TRIAGE_SOURCE_PATH
in the job and in the schedule. - Now we only need to declare
TRIAGE_SOURCE_TYPE
,TRIAGE_SOURCE_PATH
, as well as a variable per job that needs to run (e.g.TRIAGE_LABEL_ACCEPTING_MERGE_REQUESTS=1
).
- No need for declaring
- The frequency is only defined at the pipeline schedule level:
DAILY_AUTOMATION
/WEEKLY_AUTOMATION
aren't use anymore. - I've also reorganized the CI and policy files per stage (hygiene, package, close-reports) for better organization.
- Lastly, I've improved
Schedule::Manager
to remove unknown variables. A dry-run can be seen at https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/336513988.
Closes #284 (closed), #324 (closed), #325 (closed).
Edited by Rémy Coutable