Skip to content

Add run-all-jest label when triggering new pipeline on MR approval

Nao Hashizume requested to merge 379174-label-run-all-jest into master

What does this MR do and why?

This MR adds pipeline:run-all-jest label to the MR when it has any approval. Once this label is assigned to the MR, a new pipeline will be triggered and run full Jest specs (jest and jest as-if-foss jobs would be created).

Relates to gitlab-org/gitlab#379174 (closed).

Expected impact & dry-runs

Dry-run for TRIAGE_POLICY_FILE: policies/generated/default-labels.yml.erb/runner_saas.yml with TRIAGE_SOURCE_PATH: 13626558 (gitlab-org/ci-cd/tests/dind-image-tests): https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/3258980684.

There was no resource found to perform /label action, but we can see the below comment to find which labels will be applied:

80 The following comments would be posted for the rule **Add ~"group::runner", ~"devops::verify", ~"Category:Runner SaaS" to open issues**:

Action items

  • (If applicable) Add documentation to the handbook pages for Triage Operations =>
  • (If applicable) Identify the affected groups and how to communicate to them:
    • /cc @person_or_group =>
    • Relevant Slack channels =>
    • Engineering week-in-review
Edited by Nao Hashizume

Merge request reports