envoyproxy/envoy

Canary new Bazel versions and experimental flags in CI

Open

#6,857 opened on May 8, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
help wantedtech debt

Repository metrics

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

Description

To avoid surprises like the Bazel 0.25 release (which required an immediate fix and bump in https://github.com/envoyproxy/envoy/pull/6773), one approach is to add Envoy to Bazel CI in https://github.com/envoyproxy/envoy/issues/2461.

Another approach is to flip flags governing breaking behavior ahead of Bazel releases. See:

I think that if we sort https://github.com/envoyproxy/envoy/issues/2461 then we are most of the way there, but filing this in case anyone is interested in pursuing this path in the meanwhile or in parallel.

Contributor guide

Research direction
Set up Bazel CI integration for Envoy according to Bazel CI documentation and configure experimental flags following Bazel's backward compatibility policy. Refer to the linked issues and Bazelisk tool.
Tech stack
cpp
Domain
devopsci cdinfrastructure
Issue type
DevOps
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitBazel
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60