Skip to content


Here are 434 public repositories matching this topic...

psigen commented May 10, 2020

Description of the problem / feature request:

The presence of a .bazelversion file that defines any non-matching version at the root of a directory structure prevents bazel from intepreting any commands in any subdirectory, including bazel version, help, info.

However, these are the commands needed to debug why .bazelversion is not satisfied, or to query non-build-related hel

LiuVII commented Apr 3, 2019

We noticed that we have some common patterns for common conflicts/duplicate resolution in our monorepo across different binaries.

    Duplicate('^BUILD', Duplicate.SKIP),
    Duplicate('^META-INF/ASL2.0', Duplicate.SKIP),
    Duplicate('^META-INF/INDEX.LIST', Duplicate.SKIP),
    Duplicate('^META-INF/', Duplicate.SKIP
custa1200 commented Oct 7, 2019

One of the consumers of our system uses curly braces for content replacement in strings.

Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.

I have tried a number of ways to escape the braces with no luck

Other languages and templating systems seem to use the concept of using double curly b

mboes commented Sep 11, 2020

Is your feature request related to a problem? Please describe.
Running any bazel build command on a fresh system with no Python, within a workspace that uses rules_haskell, will eventually yield an error of the form:

Repository rule _config_python3_toolchain defined at:

Improve this page

Add a description, image, and links to the build-system topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the build-system topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.