bazelbuild / bazelbuild/continuous-integration

bazel-at-head-plus-downstream needs to be split and/or individual projects need to be able to add flags

Open
#709 2 comments 0 reactions 1 assignee Claimed by @fweikert View on GitHub
Dominant language
Python
Stars
302
Forks
194
Avg merge
1d 19h
Merged PRs (30d)
41

Description

Spawned from https://github.com/bazelbuild/rules_apple/issues/468.

rules_apple already has https://github.com/bazelbuild/rules_apple/blob/master/.bazelci/presubmit.yml#L17-L33, and that lets us add flags need to manually stay green on last green while addressing issue. But to stay green on bazel-at-head-plus-downstream, we have to add temp flags to our *whole* config, that means we loose the ability to ensure we don't break against the current releases because we're adding flags that really should be specific to prereleases.

I'm not sure how common this in, the python ones triggering this are especially bad because behaviors have been changed, but they don't yet work for all use cases, so there really isn't a clear path for how we'll end up having to change things, so the flag is the best choice what details are still being sorted out.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.