Run package-and-qa on feature flag config changes
What does this MR do?
If an MR includes a file in config/feature_flags/development
, this extracts the feature flag from that file and runs package-and-qa
with the flag enabled and disabled.
Testing in !69182 (closed)
Part of https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/987
Requires gitlab-qa!744 (merged) and !70038 (merged)
How to setup and validate locally (strongly suggested)
bin/qa Test::Instance::All http://localhost:3000 --set-feature-flags fork_project_form=enable
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Edited by Mark Lapierre