Only run fuzzing on commit events, not all events
What does this MR do?
API Fuzz testing today creates two pipelines for every commit, one of which is detached. This causes many extra pipelines to show up, increasing confusing and causes strange interactions with MRs.
This is because the API fuzz testing pipeline runs on both events for branch pipelines as well as merge request pipelines. Ideally, it should only be for the former, rather than the latter. This MR updates it to only run on the branch pipeline events and ignores the MR pipelines. It does this with the CI_COMMIT_BRANCH variable
This copies what we do in coverage-guided fuzzing in that template
After this change, we should see API fuzz jobs run in the same pipeline as other jobs, rather than their own pipeline.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team