continuous-integration
continuous-integration copied to clipboard
Bazel's Continuous Integration Setup
... or if it's already documented, please link to that from the [front page](https://github.com/bazelbuild/continuous-integration/blob/master/buildkite/README.md#faq). --- While trying to integrate with libraries that don't already build under Bazel it's rather common...
I want to test the following project on Bazel CI: https://github.com/Brightspace/rules_brotli I confirm that the project has a `.bazelci/presubmit.yml` file.
Currently there is no policy regulating which projects are accepted on Bazel CI. Users simply file an issue, and we periodically work through the backlog. Going forward this has to...
- I want to test the following project on Bazel CI: https://github.com/bcsgh/fm-index - I confirm that the project has a `.bazelci/presubmit.yml` file.
- I want to test the following project on Bazel CI: https://github.com/btwiuse/k0s - I confirm that the project has a `.bazelci/presubmit.yml` file.
https://buildkite.com/bazel/bcsgh-stl-to-ps/builds/8#870d8fa1-5b3a-431a-b364-f0f5c1be10af 'build' options: --cxxopt=-std=c++17 later on the C++ version ends up being C++2011: #define a(x) b(x) #define b(x) #x static_assert(__cplusplus > 201103L, a(__cplusplus)); results in: > ./tbd/ast.h:3:1: error: static assertion...
Currently the [issue template](https://github.com/bazelbuild/continuous-integration/blob/master/.github/ISSUE_TEMPLATE/adding-your-project-to-bazel-ci.md) only asks for the existence of a presubmit configuration. However, there are actually more steps for onboarding a project that depend on the project maintainer: 1....
I noticed that the tip of the master branch in the bazel-remote repository often has a red cross because the "Try Update Last Green Commit" job has failed with error...
(@philwo asked me to file an issue here) It would be great if all builds were signed At the moment release builds are signed (with .sig files etc at https://github.com/bazelbuild/bazel/releases)...
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1905#e9759395-101f-4047-b7c9-daa0fc4eb714 Broken only on Bazel@HEAD all OSes, verified it's not a one-off flake. Failure has no culprit, looks like it might be machine configuration? Not sure how to diagnose. Error...