Docker build aborted: Analysis of target '//java/com/google/copybara:copybara_deploy.jar' failed

[oldgiova]

I'm trying to build the Dockerfile from the master branch, but I'm getting this error during the bazel build:

 => ERROR [build 5/5] RUN bazel build //java/com/google/copybara:copybara_deploy.jar --java_language_version=11 --tool_java_language_version=11 --java_runtime_version=re  16.6s
------                                                                                                                                                                           
 > [build 5/5] RUN bazel build //java/com/google/copybara:copybara_deploy.jar --java_language_version=11 --tool_java_language_version=11 --java_runtime_version=remotejdk_11:    
0.208 Extracting Bazel installation...                                                                                                                                           
3.586 Starting local Bazel server and connecting to it...                                                                                                                        
4.863 Computing main repo mapping:                                                                                                                                               
5.865 Computing main repo mapping:                                                                                                                                               
6.865 Computing main repo mapping: 
7.929 Loading: 
7.931 Loading: 0 packages loaded
8.934 Loading: 0 packages loaded
8.934     currently loading: java/com/google/copybara
9.190 Analyzing: target //java/com/google/copybara:copybara_deploy.jar (1 packages loaded, 0 targets configured)
9.223 Analyzing: target //java/com/google/copybara:copybara_deploy.jar (1 packages loaded, 0 targets configured)
9.223 [0 / 1] [Prepa] BazelWorkspaceStatusAction stable-status.txt
10.57 Analyzing: target //java/com/google/copybara:copybara_deploy.jar (5 packages loaded, 6 targets configured)
10.57 [1 / 1] checking cached actions
11.61 Analyzing: target //java/com/google/copybara:copybara_deploy.jar (36 packages loaded, 8 targets configured)
11.61 [1 / 1] checking cached actions
12.61 Analyzing: target //java/com/google/copybara:copybara_deploy.jar (38 packages loaded, 8 targets configured)
12.61 [1 / 1] checking cached actions
13.62 Analyzing: target //java/com/google/copybara:copybara_deploy.jar (38 packages loaded, 8 targets configured)
13.62 [1 / 1] checking cached actions
14.82 Analyzing: target //java/com/google/copybara:copybara_deploy.jar (38 packages loaded, 8 targets configured)
14.82 [1 / 1] checking cached actions
15.82 Analyzing: target //java/com/google/copybara:copybara_deploy.jar (88 packages loaded, 412 targets configured)
15.82 [1 / 1] checking cached actions
15.83 ERROR: Analysis of target '//java/com/google/copybara:copybara_deploy.jar' failed; build aborted: module extension "non_module_deps" from "//:repositories.bzl" does not generate repository "JCommander", yet it is imported as "JCommander" in the usage at /home/ubuntu/MODULE.bazel:16:32
15.85 INFO: Elapsed time: 15.613s, Critical Path: 0.05s
15.85 INFO: 1 process: 1 internal.
15.86 ERROR: Build did NOT complete successfully
15.86 FAILED: 
------
Dockerfile:35
--------------------
  33 |     COPY . . 
  34 |     
  35 | >>> RUN bazel build //java/com/google/copybara:copybara_deploy.jar --java_language_version=11 --tool_java_language_version=11 --java_runtime_version=remotejdk_11
  36 |     
  37 |     # Use jammy to drop Python 2
--------------------
ERROR: failed to solve: process "/bin/sh -c bazel build //java/com/google/copybara:copybara_deploy.jar --java_language_version=11 --tool_java_language_version=11 --java_runtime_version=remotejdk_11" did not complete successfully: exit code: 1

I think this issue is introduced by the commit ae3ed991126159f4ce0cf27cb341da47e0608083, because if I reset the head to the previous commit d691934fcae4557ece1218eb7f8b1e51ab0a7055, the build is successful.

Thanks

[hsudhof]

Yes, the build target has to be updated. Will take a look.