Skip to content

Trigger as-if-jh pipeline if there are feature flag changes

Lin Jen-Shin requested to merge 385307-run-as-if-jh-auto-and-more into master

What does this MR do and why?

Trigger as-if-jh pipeline if there are feature flag changes

https://gitlab.com/gitlab-jh/gitlab-jh-enablement/-/issues/243 mentioned a few feature flag related changes broke JiHu default branch.

As a side note, when there's such changes, we also run package-and-test.

How often will we run this? We can probably check by commits. Running this command, showing results from 2022-11-01 til today:

git log --after=2022-11-01 --date='format:%Y-%m-%d' --format='%cd' (find {,ee/}config/feature_flags/{development,ops} -type d 2> /dev/null) | uniq -c

We get:

      8 2023-01-10
      1 2023-01-09
      1 2023-01-10
     12 2023-01-09
      1 2023-01-08
      5 2023-01-06
      1 2023-01-05
      1 2023-01-06
      8 2023-01-05
     14 2023-01-04
     14 2023-01-03
      2 2023-01-02
      2 2022-12-29
      1 2022-12-28
      7 2022-12-27
      2 2022-12-23
      5 2022-12-22
      6 2022-12-21
     12 2022-12-20
      5 2022-12-19
      2 2022-12-17
     23 2022-12-16
     22 2022-12-15
     15 2022-12-14
     11 2022-12-13
     14 2022-12-12
      2 2022-12-10
     18 2022-12-09
      6 2022-12-08
      1 2022-12-07
      3 2022-12-08
     15 2022-12-07
      1 2022-12-06
      1 2022-12-07
     15 2022-12-06
     10 2022-12-05
      1 2022-12-03
     21 2022-12-02
     12 2022-12-01
     15 2022-11-30
      9 2022-11-29
     14 2022-11-28
     10 2022-11-25
     17 2022-11-24
     10 2022-11-23
     12 2022-11-22
     10 2022-11-21
      2 2022-11-18
     10 2022-11-17
     20 2022-11-16
     11 2022-11-15
     29 2022-11-14
      3 2022-11-13
      1 2022-11-12
     11 2022-11-11
      2 2022-11-10
      1 2022-11-11
      8 2022-11-10
     19 2022-11-09
      1 2022-11-08
      1 2022-11-09
      7 2022-11-08
     14 2022-11-07
      7 2022-11-04
     17 2022-11-03
      6 2022-11-02

This might be ok?

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #385307 (closed)

Feature flag is also mentioned at https://gitlab.com/groups/gitlab-jh/-/epics/5295#note_1203603559

Edited by Lin Jen-Shin

Merge request reports