Bazel query should specify --output

[morozov]

If .bazelrc specifies any non-default query output format, skaffold will fail.

The issue has been originally reported as #1322 but then was mistakenly resolved by #1339 which was not merged and in turn was mistakenly closed by 5a519d3.

Expected behavior

Skaffold works regardless of the default output format.

Actual behavior

Skaffold cannot parse the output of bazel query since every source file is prefixed with its kind:

$ skaffold build -v debug
...
source file @go_image_base//image:000.tar.gz
source file @go_debug_image_base//image:config.json
source file @go_debug_image_base//image:001.tar.gz

Information

• Skaffold version: v0.36.0
• Operating system: Linux

Steps to reproduce the behavior

$ cd examples/bazel
$ echo "query --output=label_kind" >> .bazelrc

$ skaffold version
v0.36.0

$ skaffold build
Generating tags...
 - gcr.io/k8s-skaffold/skaffold-bazel -> gcr.io/k8s-skaffold/skaffold-bazel:v0.36.0-55-gde10d4a6-dirty
Tags generated in 17.425754ms
Checking cache...
 - gcr.io/k8s-skaffold/skaffold-bazel: FATA[0000] checking cache: getting hash for artifact gcr.io/k8s-skaffold/skaffold-bazel: getting hash for source file /BUILD: lstat source file /BUILD: no such file or directory 

Note that in the output above, "source file" is displayed as part of the name of the files which do not exist.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[morozov]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[morozov]

The kokoro job seems stuck. Is there a way to restart it?