IssueTracker

It looks like projectId inside RepoSource object for triggerTemplate is being ignored even though it shouldn't according to field description:

ID of the project that owns the Cloud Source Repository. If omitted, the project ID requesting the build is assumed.

Steps to reproduce:

• create repo-1 inside project-1
• create repo-2 inside project-2
• grant roles/source.reader (or even roles/owner) to project-1 accounts inside project-2 project IAM permissions:

serviceAccount:${project_number.project-1}@cloudbuild.gserviceaccount.com
serviceAccount:service-${project_number.project-1}@sourcerepo-service-accounts.iam.gserviceaccount.com
serviceAccount:service-${project_number.project-1}@gcp-sa-cloudbuild.iam.gserviceaccount.com
serviceAccount:${project_number.project-1}@cloudservices.gserviceaccount.com

• run commands

gcloud beta builds triggers create cloud-source-repositories --trigger-config project-2-repo-1-trigger.json --project project-1
gcloud beta builds triggers create cloud-source-repositories --trigger-config project-2-repo-2-trigger.json --project project-1

with content
project-2-repo-1-trigger.json:

{
  "description": "project-2-repo-1-trigger",
  "disabled": true,
  "filename": "cloudbuild.yaml",
  "name": "project-2-repo-1-trigger",
  "triggerTemplate": {
    "branchName": "^master$",
    "projectId": "repo-2",
    "repoName": "repo-1"
  }
}

project-2-repo-2-trigger.json:

{
  "description": "project-2-repo-2-trigger",
  "disabled": true,
  "filename": "cloudbuild.yaml",
  "name": "project-2-repo-2-trigger",
  "triggerTemplate": {
    "branchName": "^master$",
    "projectId": "repo-2",
    "repoName": "repo-2"
  }
}

Expected outcome:

• project-2-repo-1-trigger fails, because repo-1 does not exist in project-2 (only in project-1)
• project-2-repo-2-trigger succeeds (repo-2 exists in project-2)

Actual outcome:

• project-2-repo-1-trigger succeeds (ignoring projectId field and using local repo-1 instead)
• project-2-repo-2-trigger fails (ignoring projectId field and looking for repo-2 locally, which does not exist)

This looks more like a bug than a feature request, at least according to API specs.

Hello,

We have an update from the Engineering team.As of now the team has recommended that users can consider using GitHub, GitHub Enterprise, or Bitbucket Server. If there are feature gaps which prevent Users from moving to the native integration (including lack of GA-level support for GitLab.com, GitLab Enterprise Edition, or Bitbucket Cloud), we'd request users to raise feature requests to be filed outlining the specific needs.

Thank you for your trust and continued support to improve Google Cloud Platform products.