4 ms·
This sounds cool. At my current job we do multi-arch builds in GCP Cloud Build using `docker buildx`. The native `amd64` builds take like 15 minutes and the `
by dougdonohoe 4y ago
This sounds cool. At my current job we do multi-arch builds in GCP Cloud Build using `docker buildx`. The native `amd64` builds take like 15 minutes and the `arm64` component takes well over an hour with occasional time outs. We use the `--cache-to/--cache-from` to speed up repeated builds. If we can't wait the hour+ for the emulation build to run, we have a `seed-mac-arm64.sh` script that a developer (i.e., me) can run on their M1 mac to do the `arm64` half of the build, which is then picked up by GCP Cloud Build. It's a small pain, but helps us in a pinch.
This solution sounds far easier!
- jacobwg 4y agoNice, yeah we had one customer using Cloud Build, and in their case their native amd64 builds dropped from around 12 minutes to 1-2 minutes on Depot builders. Surprisingly to us, it was even faster to push from Depot to Artifact Registry than from Cloud Build directly, definitely an odd networking quirk. arm64 builds should even be a more dramatic change, they should drop to at least as fast as your current amd64 builds.
- dijit 4y agoGCP cloud build was abnormally slow in my limited testing honestly. Things that took seconds to build on my local machine were taking double-digit minutes to build in GCP. I ended up building everything with gitlab-ci using kaniko and pushing to GCR, insane speed up.