2
0
Fork 0
mirror of https://github.com/bazelbuild/rules_cc synced 2024-11-26 20:02:22 +00:00
rules_cc/.bazelci/presubmit.yml
Googler c2790137ae Stop running Buildifier as part of the presubmit
We now have copies of .bzl files that we have to keep in sync between @rules_cc and @bazel_tools/tools
I propose to re-enable the Buildifier presubmit once this issue is resolved.

*** Original change description ***

Run Buildifier as part of the presubmit.

As a result we will catch some errors already in GitHub, and not later in Critique when it's harder to fix them.

***

PiperOrigin-RevId: 265636234
Change-Id: I10730665134240b3f47950e0e8fa0add8e0bd591
2019-08-27 01:51:17 -07:00

46 lines
814 B
YAML

---
platforms:
ubuntu1604:
run_targets:
build_targets:
- "..."
test_flags:
- "--test_timeout=300"
test_targets:
- "..."
ubuntu1804:
run_targets:
build_targets:
- "..."
test_flags:
- "--test_timeout=300"
test_targets:
- "..."
ubuntu1804_nojava:
run_targets:
build_flags:
- "--javabase=@openjdk11_linux_archive//:runtime"
build_targets:
- "..."
test_flags:
- "--test_timeout=300"
- "--javabase=@openjdk11_linux_archive//:runtime"
test_targets:
- "..."
macos:
run_targets:
build_targets:
- "..."
test_flags:
- "--test_timeout=300"
test_targets:
- "..."
windows:
run_targets:
build_targets:
- "..."
test_flags:
- "--test_timeout=300"
test_targets:
- "..."