jokesterfr
commented
1 month ago | Questions | Answers |
|---|---|
| Description? | This was really hard to understand what was going wrong with docker builds here. I suspect parallelism was messing with the way we were starting / dumping / stopping MySQL in the hydration process. This ended up often with a never ending process and a costly timeout for the CI. I'm quiet sure this would sequencially build for one architecture after the other (amd64+arm64 builds). |
| Type? | bug fix / improvement / new feature / refactor |
| BC breaks? | no |
| Deprecations? | no |
| Sponsor company | Prestashop |
| Fixes | #83 #105 |
| How to test? | In actions, build a nightly for instance. See https://stackoverflow.com/questions/66303615/how-to-multiarch-build-images-sequentially-with-docker-buildx |