rollout/cli_tools_cloudbuild_build_prepare.yaml [3:17]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
timeout: 1800s

steps:
- name: 'google/cloud-sdk:alpine'
  args:
  - 'bash'
  - '-c'
  - |
    REGIONS_ARR=$(echo "$_REGIONS" | tr ";" "\n")
    TOOLS_ARR=$(echo "$_TOOLS" | tr ";" "\n")
    GCP_PROJECTS_ARR=($_IMAGE_PROJECT)

    exit_on_error() {
      ERR=$$1
      if [[ $$ERR != 0 ]]; then
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



rollout/cli_tools_cloudbuild_rollback.yaml [1:25]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
timeout: 1800s

steps:
# Rollback given tools to given locations. Expect 2 vars substitutions, examples:
# 1. $_REGIONS="us;us-east1;us-east2"
# 2. $_TOOLS="gve_vm_image_import;gce_vm_image_export"
# The script will pull the built docker images with "prev-release" tag from gcr.io (container registry),
# and then push to artifacts registry (e.g. us-east1-docker.pkg.dev/compute-image-import/wrappers/gce_vm_image_import)
# with 3 tags: the workflow execution ID, the commit SHA, and the "release".
# 1. The workflow execution ID is used to track which workflow produced the image.
# It's specifically useful when the original workflow was failed and we resumed it.
# 2. The commit SHA is used to track which version of source code produced the image.
# 3. The "release" tag marks it as the current effective image.
- name: 'google/cloud-sdk:alpine'
  args:
  - 'bash'
  - '-c'
  - |
    REGIONS_ARR=$(echo "$_REGIONS" | tr ";" "\n")
    TOOLS_ARR=$(echo "$_TOOLS" | tr ";" "\n")
    GCP_PROJECTS_ARR=($_IMAGE_PROJECT)

    exit_on_error() {
      ERR=$$1
      if [[ $$ERR != 0 ]]; then
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



