Bazel support inside gitlab-cov-fuzz

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

Users are writing fuzz tests using the built-in Bazel support. Today, GitLab fuzz testing requires a libfuzzer binary to be created to use with gitlab-cov-fuzz. This means users have to re-implement what they've already done in Bazel to be able to use fuzz testing inside GitLab.

Proposal

Allow users to specify a Bazel-produced binary as an input to gitlab-cov-fuzz. This could look like:

my_fuzz_target:
  extends: .fuzz_base
  script:
    <setup pieces here>
    - bazel build my_project # This is what users will have already
    - ./gitlab-cov-fuzz run --regression=true --engine bazel # The --engine parameter is what would be new

Additional details

An example project of building a project with Bazel and running a fuzz test against it at https://gitlab.com/stkerr/googletest-fuzzing. This could be helpful to understand how Bazel builds a project and/or how fuzz testing could be added without the built-in Bazel support.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.