Deploy
PublicDeploy Docker images and other packages
The following tasks were skipped:
- rules_proto (
Ubuntu 20.04 LTS): The same task already exists after ignoring bazel version.
- rules_proto (
macOS): The same task already exists after ignoring bazel version.
- rules_proto (
Windows): The same task already exists after ignoring bazel version.
- Bazel Examples (android (Android Firebase Cloud Messaging) on
Ubuntu 18.04 LTS (OpenJDK 11, gcc 7.5.0)): https://github.com/bazelbuild/examples/issues/487
- Bazel Examples (android (Android Firebase Cloud Messaging) on
macOS): https://github.com/bazelbuild/examples/issues/487
- Bazel Examples (android (Android NDK) on
Ubuntu 18.04 LTS (OpenJDK 11, gcc 7.5.0)): https://github.com/bazelbuild/examples/issues/501
- Bazel Examples (android (Android NDK) on
macOS arm64): https://github.com/bazelbuild/examples/issues/501
- Bazel Examples (android (Android Jetpack Compose) on
Ubuntu 18.04 LTS (OpenJDK 11, gcc 7.5.0)): Due to https://github.com/bazelbuild/examples/issues/400
- Bazel Examples (android (Android Jetpack Compose) on
macOS): Due to https://github.com/bazelbuild/examples/issues/400
- Bazel Examples (android (Android Jetpack Compose) on
Windows): Due to https://github.com/bazelbuild/examples/issues/400
- Bazel Examples (android (Android Robolectric Testing) on
Ubuntu 18.04 LTS (OpenJDK 11, gcc 7.5.0)): Due to https://github.com/bazelbuild/examples/issues/400
- Bazel Examples (android (Android Robolectric Testing) on
macOS): Due to https://github.com/bazelbuild/examples/issues/400
- Bazel Examples (configurations (configs_linux_latest) on
Ubuntu 18.04 LTS (OpenJDK 11, gcc 7.5.0)): The same task already exists after ignoring bazel version.
- Bazel Examples (configurations (configs_macos_latest) on
macOS): The same task already exists after ignoring bazel version.
- Bazel Examples (configurations (configs_windows_latest) on
Windows): The same task already exists after ignoring bazel version.
- Bazel Examples (frontend (basics_linux_latest) on
Ubuntu 20.04 LTS): The same task already exists after ignoring bazel version.
- Bazel Examples (frontend (basics_macos_latest) on
macOS): The same task already exists after ignoring bazel version.
- Bazel Examples (rules (basics_linux_latest) on
Ubuntu 22.04 LTS): The same task already exists after ignoring bazel version.
- Bazel Examples (rules (basics_macos_latest) on
macOS arm64): The same task already exists after ignoring bazel version.
- Bazel Examples (rules (basics_windows_latest) on
Windows): The same task already exists after ignoring bazel version.
- Bazel Remote Cache (gazelle & bazel mod tidy on
Ubuntu 20.04 LTS): Lockfile could change when building with Bazel@HEAD
- Bazel skylib (Last Green Bazel on
Windows): The same task already exists after ignoring bazel version.
- Bazel skylib (Latest Bazel on
Ubuntu 20.04 LTS): The same task already exists after ignoring bazel version.
- Bazel skylib (Last Green Bazel on
macOS): The same task already exists after ignoring bazel version.
- Bazel skylib (Last Green Bazel on
Ubuntu 18.04 LTS (OpenJDK 11, gcc 7.5.0)): The same task already exists after ignoring bazel version.
- Bazel skylib (Last Green Bazel on
Ubuntu 20.04 LTS): The same task already exists after ignoring bazel version.
- Buildtools (
Ubuntu 18.04 LTS (OpenJDK 11, gcc 7.5.0)): Newer abseil-cpp introduced no longer works on this old platform
- Cloud Robotics Core (
Ubuntu 18.04 LTS (OpenJDK 11, gcc 7.5.0)): True
- Stardoc (Build and test - Bazel last green - Windows on
Windows): The same task already exists after ignoring bazel version.
- Stardoc (Stardoc golden tests requiring Bazel 7.2 on
Ubuntu 20.04 LTS): Manual tests requiring an older Bazel version
- Stardoc (Build and test - Bazel last green on
macOS): The same task already exists after ignoring bazel version.
- Stardoc (Build and test - Bazel last green on
Ubuntu 18.04 LTS (OpenJDK 11, gcc 7.5.0)): The same task already exists after ignoring bazel version.
- Stardoc (Build and test - Bazel last green on
Ubuntu 20.04 LTS): The same task already exists after ignoring bazel version.
- rules_apple (Last Green Bazel on
macOS arm64): The same task already exists after ignoring bazel version.
- rules_foreign_cc (Minimum Supported Version on
Ubuntu 18.04 LTS (OpenJDK 11, gcc 7.5.0)): Duplicates tests in other targets
- rules_foreign_cc (Minimum Supported Version Examples on
Ubuntu 18.04 LTS (OpenJDK 11, gcc 7.5.0)): Duplicates tests in other targets
- rules_jvm_external (
Ubuntu 22.04 LTS): The same task already exists after ignoring bazel version.
- rules_jvm_external (
Ubuntu 22.04 LTS): The same task already exists after ignoring bazel version.
- rules_python (Gazelle: workspace, minumum supported Bazel version on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_python (Default: Ubuntu, workspace, minimum Bazel on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_python (Default: Ubuntu, bzlmod, minimum Bazel on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_python (Default test: Ubuntu, Pystar, bzlmod on
Ubuntu 20.04 LTS): The same task already exists after ignoring bazel version.
- rules_python (RBE: Ubuntu, minimum Bazel on RBE
Ubuntu 16.04 LTS (OpenJDK 8, gcc 5.4.0)): Bazel 6 required
- rules_python (examples/build_file_generation: Ubuntu, workspace, minimum Bazel on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_python (examples/bzlmod: Ubuntu, minimum Bazel on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_python (examples/bzlmod: Ubuntu with lockfile on
Ubuntu 20.04 LTS): Lockfile depends on the bazel version
- rules_python (examples/bzlmod: macOS with lockfile on
macOS): Lockfile depends on the bazel version
- rules_python (examples/bzlmod_build_file_generation: Ubuntu, minimum Bazel on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_python (examples/pip_parse: Ubuntu, workspace, minimum supporte Bazel version on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_python (examples/pip_parse: Ubuntu, bzlmod, minimum supporte Bazel version on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_python (examples/pip_parse_vendored: Ubuntu, workspace, minimum Bazel on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_python (examples/pip_parse_vendored: Ubuntu, bzlmod, minimum Bazel on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_python (compile_pip_requirements_test_from_external_repo: Ubuntu, workspace, minimum Bazel on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_python (compile_pip_requirements_test_from_external_repo: Ubuntu, bzlmod, minimum Bazel on
Ubuntu 20.04 LTS): Bazel 6 required
- rules_testing (Workspace (Bazel 5.x) on
macOS): Already tested on latest
- rules_testing (Workspace (Bazel 5.x) on
Ubuntu 20.04 LTS): Already tested on latest
- rules_testing (Workspace (Bazel 5.x) on
Windows): Already tested on latest
- rules_swift (Current LTS using bzlmod on
macOS arm64): The same task already exists after ignoring bazel version.
- rules_swift (Last Green Bazel on
macOS arm64): The same task already exists after ignoring bazel version.
- rules_swift (Current LTS on
Ubuntu 20.04 LTS): The same task already exists after ignoring bazel version.
- rules_swift (Last Green Bazel on
Ubuntu 20.04 LTS): The same task already exists after ignoring bazel version.
Downstream testing is disabled for the following projects
- Android Testing: https://github.com/android/testing-samples/issues/417
- Bazel Codelabs: https://github.com/bazelbuild/codelabs/issues/38
- Bazel watcher: https://github.com/bazelbuild/bazel-watcher/issues/590
- Cartographer: https://github.com/cartographer-project/cartographer/issues/1938#issuecomment-1804795113
- Envoy: https://github.com/envoyproxy/envoy/issues/29723
- FlatBuffers: https://github.com/google/flatbuffers/issues/7992
- TensorFlow: https://github.com/tensorflow/tensorflow/issues/60508
- rules_cc: https://github.com/bazelbuild/rules_cc/issues/190
- rules_graalvm: https://github.com/sgammon/rules_graalvm/issues/409
- rules_jsonnet: https://github.com/bazelbuild/rules_jsonnet/issues/194
- rules_rust: https://github.com/bazelbuild/rules_rust/issues/2519, https://github.com/bazelbuild/rules_rust/issues/2464
- rules_scala: waiting on https://github.com/bazelbuild/rules_scala/pull/1422
bin/ci-builder run nightly ci/deploy/devsite.shbin/ci-builder run nightly ci/deploy/devsite.sh
Waited 50s
Ran in 17m 13s
bin/ci-builder run stable bin/pyactivate -m ci....bin/ci-builder run stable bin/pyactivate -m ci.deploy.docker
Waited 46s
Ran in 4m 16s
bin/ci-builder run stable bin/pyactivate -m ci....bin/ci-builder run stable bin/pyactivate -m ci.deploy.pypi
Waited 49s
Ran in 3m 19s
bin/ci-builder run stable bin/pyactivate -m ci....bin/ci-builder run stable bin/pyactivate -m ci.deploy.npm
Waited 49s
Ran in 4m 19s
Total Job Run Time: 30m 12s