BuildFileNotFoundException: no such package '@@[unknown repo 'buildkite_config' requested from @@]//config': The repository '@@[unknown repo 'buildkite_config' requested from @@]' could not be resolved: No repository visible as '@buildkite_config' from main repository

[sgowroji]

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/3599#018d1aba-e116-47ac-bd22-d9b2ca73bcc5

Platform: Ubuntu

Logs:

(04:01:57) ERROR: /var/lib/buildkite-agent/builds/bk-docker-w343/bazel-org-repo-root/rules_nodejs/e2e/smoke/BUILD.bazel:156:8: com.google.devtools.build.lib.packages.BuildFileNotFoundException: no such package '@@[unknown repo 'buildkite_config' requested from @@]//config': The repository '@@[unknown repo 'buildkite_config' requested from @@]' could not be resolved: No repository visible as '@buildkite_config' from main repository
(04:01:57) ERROR: Analysis of target '//:require_acorn' failed; build aborted

Bzlmod is enabled by default at HEAD, Requires a fix in the configuration.

Culprit: https://github.com/bazelbuild/bazel/commit/30d033cd7e2153e8b8d7eb034a5323053192ecaa

Steps:

git clone -v https://github.com/bazelbuild/rules_nodejs.git 
git reset 9898ac17be19f7a4a268ba7123e969bcc6f693b6 --hard
export USE_BAZEL_VERSION=3e7052824b54158d72e4b07d6330aa41a9857707
cd e2e/smoke
bazel build //... 

CC Greenteam @meteorcloudy

[sgowroji]

CC @alexeagle @gregmagolan

[alexeagle]

buildkite_config doesn't seem like anything in rules_nodejs. Is this something now expected by the Bazel CI?

[sgowroji]

@meteorcloudy Can you please guide on the above comments. Thanks

[meteorcloudy]

Yes, it's required by Bazel CI to run with RBE. It's defined in one of the smoke test: https://github.com/bazelbuild/rules_nodejs/blob/9898ac17be19f7a4a268ba7123e969bcc6f693b6/e2e/smoke/WORKSPACE.bazel#L57-L62

However, in the downstream pipeline, Bzlmod is enabled at HEAD and there is a WORKSPACE.bzlmod file there. So moving the definition to MODULE.bazel or WORKSPACE.bzlmod could solve this problem.

[sgowroji]

Hi @alexeagle, Any update on the above failures ?

[sgowroji]

Hi @alexeagle, Above CI is still failing in Downstream, We will be moving it to Disabled CI pipelines until this issue gets fixed. Thanks!

[sgowroji]

CI is Green now in Disabled Pipeline. Closing this issue now and enabling the rules_nodejs in downstream CI