The GitHub Actions job "Release PROD images" on airflow.git/use-merge-for-multiplatform-images has failed. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 0ef146a5e6fc61c3004f6158a02fe5dca73bb58f / Jarek Potiuk <[email protected]> Separate building release images to separate hardware So far, when we built release images in CI or locally we relied on either the emulation or having a builder configured that could handle having docker engines running at the same time on different hardware. That had some disadvantages: * for emulation, it was terribly slow.It was 10/15 times slower than building appropriate platform on appropriate hardware - making our image relase process taking more than hour. Also build output from both runs was interleaved which made it rather difficult to diagnose problems sometimes. * for using local builder, you needed to setup and authenticate with another docker engine, which required SSH connectivity and port forwarding and it was really not feasible for GitHub Actions where you cannot easily authenticate between separate runners and make sure they are reachable from each other. This PR implements different appreach - merging build images. Instead of building them together, the images are built as ``digest-only`` images and pushed to the registry and their metadata with digest is uploaded as artifacts. Then a separate merge step downloads the metadata and creates merged manifest where both images are referred to. This allows to build each image separately on a separate hardware - way faster in general (providing that we have an appropriate hypervisor capable hardware for each platform that we can build the images on. Report URL: https://github.com/apache/airflow/actions/runs/14821841983 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
