CI/CD: Add aliased TARGETARCH builds - #561
Conversation
|
The main problem with supporting the TARGETARCH naming pattern is that it duplicates the artifacts. Please read this thread. I understand this is inconvenient, but I'm not convinced providing twice the amount of files under different names is the answer. |
But still the workaround can be implemented so fellow devs don't suffer. |
|
I'm not adding an exception for aarch64. If you want the problem to be solved, please suggest a solution that works for all architectures. This is not an easy task; we've thought about it, and haven't found anything satisfactory. It's not only a question of storage, it's also a question of clarity for users. If two tarballs with different names are effectively the same, this can cause confusion. Having GitHub support for explicit symlinks (displayed as such in the downloads page) would solve both problems at once. Unfortunately, it's not under our control. |
Issue:
$TARGETARCHenv variable for aarch64 is set toarm64, so each multi-arch dependent project have to implement if statement replacingarm64 -> aarch64in their Dockerfile.Solution:
aarch64 -> arm64archive in CI