Change bazel usage with cloud-sdk container image for release flow

Release workflow tested with
`gcloud builds submit --config=release/cloudbuild.yaml
--substitutions=_BUILD_GCR="${BUILD_GCR}",_RELEASE_GCR="${RELEASE_GCR}"`

from the root dir of the project using dev bucket for BUILD/RELEASE_GCR.
The release git trigger is configured to run from the root of the cos/tools repo.

Change-Id: I8c4d6a7f7d9bdf1dd3d305735c6dd777ce44e293
Reviewed-on: https://cos-review.googlesource.com/c/cos/tools/+/21871
Reviewed-by: Robert Kolchmeyer <rkolchmeyer@google.com>
Tested-by: Arnav Kansal <rnv@google.com>
Cloud-Build: GCB Service account <228075978874@cloudbuild.gserviceaccount.com>
4 files changed
tree: 4a8a35f76a3f0a9a5478802b92781f8827743548
  1. release/
  2. src/
  3. testing/
  4. BUILD.bazel
  5. cloudbuild.yaml
  6. CONTRIBUTING.md
  7. deps.bzl
  8. go.mod
  9. go.sum
  10. LICENSE
  11. README.md
  12. run_tests.sh
  13. WORKSPACE
README.md

Tools for Container-Optimized OS

This is a repository of various tools developed for Container-Optimized OS. Examples include cos-gpu-installer, cos-toolbox, etc.

See CONTRIBUTING.md for how to contribute.