search

bazelbuild / rules_k8s

This repository contains rules for interacting with Kubernetes configurations / clusters.
Apache License 2.0
290 stars 137 forks source link

rules_k8s broken with Bazel@HEAD CI #668

Open c-parsons opened 3 years ago

c-parsons commented 3 years ago

Breakage: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2211#845f819e-3ae0-457b-8389-4e381d5e7168


(16:09:28) ERROR: /var/lib/buildkite-agent/builds/bk-docker-53p6/bazel-downstream-projects/rules_k8s/examples/hellogrpc/BUILD:61:16: in jsonnet_to_json rule //examples/hellogrpc:deployment:
--
  | Traceback (most recent call last):
  | File "/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/40d71967fca1731c50aad85c7f24c1eb/external/io_bazel_rules_jsonnet/jsonnet/jsonnet.bzl", line 239, column 34, in _jsonnet_to_json_impl
  | transitive_files = depset(transitive_data),
  | Error in depset: parameter 'direct' must contain a list of elements, and may no longer accept a depset. The deprecated behavior may be temporarily re-enabled by setting --incompatible_disable_depset_items=false
  | (16:09:28) ERROR: /var/lib/buildkite-agent/builds/bk-docker-53p6/bazel-downstream-projects/rules_k8s/examples/hellogrpc/BUILD:61:16: Analysis of target '//examples/hellogrpc:deployment' failed

Bazel instituted a change to semantics of depset(). This should be fixed in-place or you can temporarily use --incompatible_disable_depset_items=false to disable this restriction.

meteorcloudy commented 2 years ago

I'm disabling rules_k8s in downstream due to this issue