continuous-integration icon indicating copy to clipboard operation
continuous-integration copied to clipboard

Bazel's Continuous Integration Setup

Results 162 continuous-integration issues
Sort by recently updated
recently updated
newest added

This FR is brought up by @ulfjack at https://github.com/bazelbuild/bazel/issues/10425#issuecomment-566430329

To at least try to prevent bugs like https://github.com/bazelbuild/bazel/issues/10328.

Looking at https://github.com/bazelbuild/rules_apple/commits/master and https://github.com/bazelbuild/rules_swift/commits/master, the majority of the recent commits show a yellow dot because some checks haven't completed. If you click thru to the buildkite pages, they appear...

I thought that a newer run of the same CL would cancel any old runs, but it seems it doesn't work anymore: ![wAXS3DWNX3R](https://user-images.githubusercontent.com/418721/66738300-68963b00-ee6e-11e9-8337-1d3aed8cfbbd.png) Perhaps caused by skipped mac os presubmit...

For the bazelbuild/skydoc repository, I'd like to introduce a number of Starlark "testdata" bzl files. These files are for testing purposes only, and, by design, they will not always abide...

`--incompatible_windows_style_arg_escaping` is a startup flag, but the pipeline used it as a build flag. See https://buildkite.com/bazel/bazelisk-plus-incompatible-flags/builds/57#job-bc144aea-5307-4f65-ab8b-89553d11cc22 @laurentlb : possibly a bug in Bazelisk's `--migration` flag

FR
P2

I'd like to exclude my docs/ directory from `build_targets` because it depends on an unreleased bazel version to build (i.e., regenerate the documentation) successfully. Until that newer bazel is out...

In my new Bazel test rule implementation I wasn't declaring all files properly and everything worked locally. I declared a file and copied a directory containing other files into that...

Projects to be enabled on Windows: Belongs to Bazel team: - [ ] Android Studio Plugin - [ ] Android Testing - [X] Bazel - [ ] Bazel Bench -...

P2
product excellence

rules_go fails with bazel@HEAD, but it doesn't seem tied to any particular bazel commit. The failing tests are coverage-related, and seem to be that the coverage file is not found...