Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation issue: Remote caching #12764

Open
symbiont-ji opened this issue Jan 1, 2021 · 2 comments
Open

Documentation issue: Remote caching #12764

symbiont-ji opened this issue Jan 1, 2021 · 2 comments
Labels
help wanted Someone outside the Bazel team could own this P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Remote-Exec Issues and PRs for the Execution (Remote) team type: documentation (cleanup)

Comments

@symbiont-ji
Copy link

Documentation URL: https://docs.bazel.build/versions/master/remote-caching.html

Where is the documentation for how to provide bazel options to use grpcs as a remote cache? In particular, what formats are the keys and certs supposed to be in? I used:

bazel build \
  --remote_cache=grpcs://192.0.2.42:8086 \
  --tls_certificate=ca.pem \
  --tls_client_certificate=client.pem \
  --tls_client_key=client-key.pem \
  //...

and got a complaint about the client key being in the wrong format. Some searching revealed that it should have been in PKCS#8 format, so I converted it and ran:

bazel build \
  --remote_cache=grpcs://192.0.2.42:8086 \
  --tls_certificate=ca.pem \
  --tls_client_certificate=client.pem \
  --tls_client_key=client-key.p8 \
  //...

Which gave me the singularly unenlightening message: ERROR: Failed to query remote execution capabilities: General OpenSslEngine problem (I guess saying what the problem was is too much effort?)

The help message isn't enlightening either:

$ bazel help build | grep tls_client_key
  --tls_client_key (a string; default: see description)

What description?

@mostynb
Copy link
Contributor

mostynb commented Jan 1, 2021

This recipe was used to create self-signed certs/keys for tests, it might be a good starting point in figuring this out:
https://github.com/bazelbuild/bazel/tree/master/src/test/testdata/test_tls_certificate

@aiuto aiuto added team-Remote-Exec Issues and PRs for the Execution (Remote) team type: documentation (cleanup) untriaged labels Jan 6, 2021
@symbiont-ji
Copy link
Author

symbiont-ji commented Jan 6, 2021 via email

@philwo philwo added P3 We're not considering working on this, but happy to review a PR. (No assignee) and removed untriaged labels Feb 9, 2021
@ShreeM01 ShreeM01 added the team-Documentation Documentation improvements that cannot be directly linked to other team labels label Jan 10, 2023
@keertk keertk added the help wanted Someone outside the Bazel team could own this label Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Someone outside the Bazel team could own this P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Remote-Exec Issues and PRs for the Execution (Remote) team type: documentation (cleanup)
Projects
None yet
Development

No branches or pull requests

7 participants
@philwo @aiuto @mostynb @symbiont-ji @ShreeM01 @keertk and others