Hi,
I'm wondering if there is a way one can use Google Cloud Build with multiple repositories, without having to keep the `cloudbuild.yaml` file inside each one (suppose it would be the same configuration for each of those repositories). On the "Edit trigger" page (
https://console.cloud.google.com/cloud-build/triggers/<random-guid>?project=<projectID>), the Build configuration section has two options, one for Dockerfile and one for Cloud Build configuration file (yaml or json). The
Learn more link under that second option states that "You must create the build config file in your project's root directory and Cloud Build will read it each time it starts a build."
Given that restriction, I thought a workaround would be to have a separate repository, specifically for that config file (and any other related dependencies), and have that one for the Cloud Build trigger. But in that case, that trigger would not be run whenever changes are made to the original repos since they are separate.
I'm asking about because I work at a place which relies on Cloudbees Jenkins for CI/CD, and separate repos for each of the React UI "modules" which make up our applications. This type of "external config" in question would be a requirement to even consider switching to Cloud Build (which I hope happens).
-Pat