To be honest I never optimized my setup to a single artifact level. The way I set up this was that in a Google Cloud Storage bucket I have a subfolder for each

To be honest I never optimized my setup to a single artifact level. The way I set up this was that in a Google Cloud Storage bucket I have a subfolder for each build whose name is monotonically increasing (ie by including time in the folder name like 20220225_23_49_50/bazel-* folders). That way I can copy the latest build to the cloud build VM and still retain history. The object lifecycle settings I use keep artifacts around for 1 month and I never had the need to find something outside that time window. There could be smarter ways to do so tbh, like having time&date_<Sha of commit>, but I didn't have the need for any of that yet. About GitHub I am not sure, bit cloud build can be triggered by GitHub commits: https://cloud.google.com/build/docs/automating-builds/build-repos-from-github https://cloud.google.com/build/docs/automating-builds/build-... . I hope it helps!