GitHub\'s Google Cloud Build integration does not detect a cloudbuild.yaml
or Dockerfile
if it is not in the root of the repository.
When
We are migrating to a mono-repo right now, and I haven't found any CI/CD solution that handles this well.
The key is to not only detect changes, but also any services that depend on that change. Here is what we are doing:
make build
on any service that is affected by the change. So far it is working well, but I totally understand if this doesn't fit your workflow.
Another option many people use is Bazel. Not the most simple tool, but especially great if you have many different languages or build processes across your mono repo.
You can create a build trigger for your repository. When setting up a trigger with cloudbuild.yaml
for build configuration, you need to provide the path to the cloudbuild.yaml
within the repository.
You can do this by adding a cloudbuild.yaml
in the root of your repository with a single gcr.io/cloud-builders/gcloud
step. This step should:
find
to locate additional cloudbuild.yaml
files.cloudbuild.yaml
, fork and submit a build by running gcloud builds submit
.gcloud
commands to complete.There's a good example of one way to do this in the root cloudbuild.yaml within the GoogleCloudPlatform/cloud-builders-community repo.
If we strip out the non-essential parts, basically you have something like this:
steps:
- name: 'gcr.io/cloud-builders/gcloud'
entrypoint: 'bash'
args:
- '-c'
- |
for d in */; do
config="${d}cloudbuild.yaml"
if [[ ! -f "${config}" ]]; then
continue
fi
echo "Building $d ... "
(
gcloud builds submit $d --config=${config}
) &
done
wait