bazel
/
bazel-skylib
mirror of https://github.com/bazelbuild/bazel-skylib
2
0
Fork 0
Code Issues Releases Activity
bazel-skylib/.bazelci/presubmit.yml

95 lines
2.1 KiB
YAML
Raw Normal View History

add buildkite to bazel's new ci we'll run skylib as a postsubmit project and before every release to ensure we don't break it.
2018-02-25 11:07:47 +00:00
---
Add gazelle plugin to CI and distribution mechanism (#424) After #400, the gazelle plugin has been cleanly separated out into its own bazel workspace, which will soon finally allow us to mark it stable. But this means: * we need to change our bazelci config to explicitly build and test it, since `bazel build //...` no longer includes the plugin; * we need to add proper distribution rules for it; * we need to update release instructions, since now we will have two distribution tarballs
2023-01-20 21:48:10 +00:00
.reusable_config: &reusable_config
build_targets:
- "--"
- "//..."
- "@bazel_skylib_gazelle_plugin//..."
test_targets:
- "--"
- "//..."
- "@bazel_skylib_gazelle_plugin//..."
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
tasks:
ubuntu1804_latest:
Add gazelle plugin to CI and distribution mechanism (#424) After #400, the gazelle plugin has been cleanly separated out into its own bazel workspace, which will soon finally allow us to mark it stable. But this means: * we need to change our bazelci config to explicitly build and test it, since `bazel build //...` no longer includes the plugin; * we need to add proper distribution rules for it; * we need to update release instructions, since now we will have two distribution tarballs
2023-01-20 21:48:10 +00:00
<<: *reusable_config
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
name: "Latest Bazel"
platform: ubuntu1804
bazel: latest
Add basic shell testing for unittest.bzl (#108)
2019-02-11 22:18:56 +00:00
test_flags:
- "--test_env=PATH"
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
ubuntu1604_latest:
Add gazelle plugin to CI and distribution mechanism (#424) After #400, the gazelle plugin has been cleanly separated out into its own bazel workspace, which will soon finally allow us to mark it stable. But this means: * we need to change our bazelci config to explicitly build and test it, since `bazel build //...` no longer includes the plugin; * we need to add proper distribution rules for it; * we need to update release instructions, since now we will have two distribution tarballs
2023-01-20 21:48:10 +00:00
<<: *reusable_config
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
name: "Latest Bazel"
platform: ubuntu1604
bazel: latest
Add basic shell testing for unittest.bzl (#108)
2019-02-11 22:18:56 +00:00
test_flags:
- "--test_env=PATH"
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
macos_latest:
Add gazelle plugin to CI and distribution mechanism (#424) After #400, the gazelle plugin has been cleanly separated out into its own bazel workspace, which will soon finally allow us to mark it stable. But this means: * we need to change our bazelci config to explicitly build and test it, since `bazel build //...` no longer includes the plugin; * we need to add proper distribution rules for it; * we need to update release instructions, since now we will have two distribution tarballs
2023-01-20 21:48:10 +00:00
<<: *reusable_config
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
name: "Latest Bazel"
platform: macos
bazel: latest
Add basic shell testing for unittest.bzl (#108)
2019-02-11 22:18:56 +00:00
test_flags:
- "--test_env=PATH"
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
windows_latest:
Add gazelle plugin to CI and distribution mechanism (#424) After #400, the gazelle plugin has been cleanly separated out into its own bazel workspace, which will soon finally allow us to mark it stable. But this means: * we need to change our bazelci config to explicitly build and test it, since `bazel build //...` no longer includes the plugin; * we need to add proper distribution rules for it; * we need to update release instructions, since now we will have two distribution tarballs
2023-01-20 21:48:10 +00:00
<<: *reusable_config
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
name: "Latest Bazel"
platform: windows
bazel: latest
e2e tests: make them run on Windows (#121)
2019-03-19 12:37:33 +00:00
test_flags:
# TODO(laszlocsomor): remove "--test_env=LOCALAPPDATA" after
# https://github.com/bazelbuild/bazel/issues/7761 is fixed
- "--test_env=LOCALAPPDATA"
Add diff_test asserting that docs are up-to-date (#321) Based on Aspect's stardoc_with_diff_test; see https://github.com/aspect-build/bazel-lib/blob/main/docs/docs.md
2022-03-29 19:14:07 +00:00
- "--test_tag_filters=-no_windows"
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
ubuntu1804_last_green:
Add gazelle plugin to CI and distribution mechanism (#424) After #400, the gazelle plugin has been cleanly separated out into its own bazel workspace, which will soon finally allow us to mark it stable. But this means: * we need to change our bazelci config to explicitly build and test it, since `bazel build //...` no longer includes the plugin; * we need to add proper distribution rules for it; * we need to update release instructions, since now we will have two distribution tarballs
2023-01-20 21:48:10 +00:00
<<: *reusable_config
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
name: "Last Green Bazel"
platform: ubuntu1804
bazel: last_green
test_flags:
- "--test_env=PATH"
ubuntu1604_last_green:
Add gazelle plugin to CI and distribution mechanism (#424) After #400, the gazelle plugin has been cleanly separated out into its own bazel workspace, which will soon finally allow us to mark it stable. But this means: * we need to change our bazelci config to explicitly build and test it, since `bazel build //...` no longer includes the plugin; * we need to add proper distribution rules for it; * we need to update release instructions, since now we will have two distribution tarballs
2023-01-20 21:48:10 +00:00
<<: *reusable_config
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
name: "Last Green Bazel"
platform: ubuntu1604
bazel: last_green
test_flags:
- "--test_env=PATH"
macos_last_green:
Add gazelle plugin to CI and distribution mechanism (#424) After #400, the gazelle plugin has been cleanly separated out into its own bazel workspace, which will soon finally allow us to mark it stable. But this means: * we need to change our bazelci config to explicitly build and test it, since `bazel build //...` no longer includes the plugin; * we need to add proper distribution rules for it; * we need to update release instructions, since now we will have two distribution tarballs
2023-01-20 21:48:10 +00:00
<<: *reusable_config
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
name: "Last Green Bazel"
platform: macos
bazel: last_green
test_flags:
- "--test_env=PATH"
windows_last_green:
Add gazelle plugin to CI and distribution mechanism (#424) After #400, the gazelle plugin has been cleanly separated out into its own bazel workspace, which will soon finally allow us to mark it stable. But this means: * we need to change our bazelci config to explicitly build and test it, since `bazel build //...` no longer includes the plugin; * we need to add proper distribution rules for it; * we need to update release instructions, since now we will have two distribution tarballs
2023-01-20 21:48:10 +00:00
<<: *reusable_config
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
name: "Last Green Bazel"
platform: windows
bazel: last_green
e2e tests: make them run on Windows (#121)
2019-03-19 12:37:33 +00:00
test_flags:
# TODO(laszlocsomor): remove "--test_env=LOCALAPPDATA" after
# https://github.com/bazelbuild/bazel/issues/7761 is fixed
- "--test_env=LOCALAPPDATA"
Add diff_test asserting that docs are up-to-date (#321) Based on Aspect's stardoc_with_diff_test; see https://github.com/aspect-build/bazel-lib/blob/main/docs/docs.md
2022-03-29 19:14:07 +00:00
- "--test_tag_filters=-no_windows"
CI updates. (#118) - Retire the use of travis for testing. - Update buildkite config: - Enable buildifier testing (close to what was on travis, and is being improved.) - Update the config to now test the latests release and the latest green, replacing the "head" testing on travis.
2019-02-27 17:21:18 +00:00
feat: bzlmod setup (#385) Creates MODULE.bazel and WORKSPACE.bzlmod files to enable bazel-skylib to work with the `--experimental_enable_bzlmod` flag. rules_go has been updated as the previously used version is not available in the BCR. stardoc has been updated due to a strange issue with Bzlmod enabled that caused the `diff_test` and `unittest` docs to be generated without any contents that was magically fixed upon updating. bazelbuild/bazel-central-registry#124 Co-authored-by: Alexandre Rostovtsev <arostovtsev@google.com>
2022-08-30 18:57:34 +00:00
ubuntu1804_last_green_bzlmod:
Add gazelle plugin to CI and distribution mechanism (#424) After #400, the gazelle plugin has been cleanly separated out into its own bazel workspace, which will soon finally allow us to mark it stable. But this means: * we need to change our bazelci config to explicitly build and test it, since `bazel build //...` no longer includes the plugin; * we need to add proper distribution rules for it; * we need to update release instructions, since now we will have two distribution tarballs
2023-01-20 21:48:10 +00:00
<<: *reusable_config
feat: bzlmod setup (#385) Creates MODULE.bazel and WORKSPACE.bzlmod files to enable bazel-skylib to work with the `--experimental_enable_bzlmod` flag. rules_go has been updated as the previously used version is not available in the BCR. stardoc has been updated due to a strange issue with Bzlmod enabled that caused the `diff_test` and `unittest` docs to be generated without any contents that was magically fixed upon updating. bazelbuild/bazel-central-registry#124 Co-authored-by: Alexandre Rostovtsev <arostovtsev@google.com>
2022-08-30 18:57:34 +00:00
name: "Last Green Bazel (with bzlmod)"
platform: ubuntu1804
bazel: last_green
build_flags:
- "--experimental_enable_bzlmod"
test_flags:
- "--experimental_enable_bzlmod"
- "--test_env=PATH"
Fix Buildifier version (#124) "buildifier: true" has been deprecated by https://github.com/bazelbuild/continuous-integration/pull/542
2019-03-07 15:27:25 +00:00
buildifier: latest