IssueTracker

This will create a public issue which anybody can view and comment on.

Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.

Problem you have encountered: While our bitbucket-backed Cloud Build trigger performs the CI/CD script we have defined to deploy a Cloud Run instance, the UI continuously notifies us our CI/CD is incomplete (see image #2). It suggests we provide the name of the trigger used to complete the set-up, but fails to recognize it. (see image #2

What you expected to happen: I expect for the setup to complete when I provide an existing trigger name to the trigger name input box.

Steps to reproduce: deploy a Cloud Run instance from a bitBucket server repository.

  - name: gcr.io/cloud-builders/docker
    id: "build-image"
    script: > 
      docker build -t
      $_AR_HOSTNAME/$PROJECT_ID/$_REPO_NAME/$_SERVICE_NAME:latest
      -f Dockerfile . --network=cloudbuild
    automapSubstitutions: true


  # Push the container image to Container Registry
  - name: "gcr.io/cloud-builders/docker"
    id: "push-image"
    args:
      ["push", "$_AR_HOSTNAME/$PROJECT_ID/$_REPO_NAME/$_SERVICE_NAME:latest"]


  - name: "gcr.io/google.com/cloudsdktool/cloud-sdk:slim"
    id: "create-cloudrun"
    waitFor: ["build-image", "push-image"]
    args:
      - run
      - deploy
      - $_CLOUDRUN_NAME
      - "--platform=managed"
      - >-
        --image=$_AR_HOSTNAME/$PROJECT_ID/$_REPO_NAME/$_SERVICE_NAME:latest
      - >-
        --labels=managed-by=gcp-cloud-build-deploy-cloud-run,commit-sha=$COMMIT_SHA,gcb-build-id=$BUILD_ID,gcb-trigger-id=$_TRIGGER_ID
      - "--region=$_DEPLOY_REGION"
      - "--quiet"
      - "--execution-environment=gen1"
      - "--port=8080"
      - "--allow-unauthenticated"
    entrypoint: gcloud
images:
  - >-
    $_AR_HOSTNAME/$PROJECT_ID/$_REPO_NAME/$_SERVICE_NAME:latest
options:
  substitutionOption: ALLOW_LOOSE
tags:
  - gcp-cloud-build-deploy-cloud-run
  - gcp-cloud-build-deploy-cloud-run-managed
  - cr-reg2vec-service-$_ENV_NAME```


Other information (workarounds you have tried, documentation consulted, etc):