Bazel makes sense in the Prow jobs because those often get invoked with a pre-populated Bazel cache. But local invocation don't need it and now can turn it off with CSI_PROW_USE_BAZEL=false.
| Name |
Last commit
|
Last update |
|---|---|---|
| .prow.sh | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| LICENSE | Loading commit data... | |
| OWNERS | Loading commit data... | |
| README.md | Loading commit data... | |
| RELEASE.md | Loading commit data... | |
| SECURITY_CONTACTS | Loading commit data... | |
| SIDECAR_RELEASE_PROCESS.md | Loading commit data... | |
| build.make | Loading commit data... | |
| cloudbuild.sh | Loading commit data... | |
| cloudbuild.yaml | Loading commit data... | |
| code-of-conduct.md | Loading commit data... | |
| filter-junit.go | Loading commit data... | |
| go-get-kubernetes.sh | Loading commit data... | |
| prow.sh | Loading commit data... | |
| travis.yml | Loading commit data... | |
| update-vendor.sh | Loading commit data... | |
| util.sh | Loading commit data... | |
| verify-go-version.sh | Loading commit data... | |
| verify-shellcheck.sh | Loading commit data... | |
| verify-subtree.sh | Loading commit data... | |
| verify-vendor.sh | Loading commit data... |