Commit 4a2caedc authored by Nick Gaskill's avatar Nick Gaskill

Merge branch 'update-fuzz-docs-with-yaml-keys' into 'master'

Add YAML keys that user must not override

See merge request gitlab-org/gitlab!38067
parents 06dd5868 fc28aee6
...@@ -49,6 +49,14 @@ targets. Each fuzz target **must** have a separate job. For example, the ...@@ -49,6 +49,14 @@ targets. Each fuzz target **must** have a separate job. For example, the
[go-fuzzing-example project](https://gitlab.com/gitlab-org/security-products/demos/go-fuzzing-example) [go-fuzzing-example project](https://gitlab.com/gitlab-org/security-products/demos/go-fuzzing-example)
contains one job that extends `.fuzz_base` for its single fuzz target. contains one job that extends `.fuzz_base` for its single fuzz target.
Note that the hidden job `.fuzz_base` uses several YAML keys that you must not override in your own
job. If you include these keys in your own job, you must copy their original content. These keys
are:
- `before_script`
- `artifacts`
- `rules`
The `my_fuzz_target` job (the separate job for your fuzz target) does the following: The `my_fuzz_target` job (the separate job for your fuzz target) does the following:
- Extends `.fuzz_base`. - Extends `.fuzz_base`.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment