envoyproxy/envoy

Use ClusterFuzz corpus in CI

Open

#4,263 opened on Aug 27, 2018

View on GitHub
 (2 comments) (2 reactions) (0 assignees)C++ (5,373 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

We may be able to avoid regressions such as the one patched in https://github.com/envoyproxy/envoy/pull/4245 if we have CI download the corpus assembled by ClusterFuzz and verify against this prior to merge.

This would require a new CI target, which would be somewhat non-hermetic, as it would fetch from the ClusterFuzz GCS buckets for Envoy on each run.

CC @kcc @dor1s

Contributor guide

Research direction
Examine Envoy's CI configuration to understand how to add a new target; then investigate how to download the ClusterFuzz corpus from GCS and integrate it into the test suite.
Tech stack
cpp
Domain
backenddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++GitCI/CD
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45