How do you handle your CI jobs when compiling seve...
# multiplatform
m
How do you handle your CI jobs when compiling several multiplatform targets? Our build just went from 40min to a whooping 1h20 when adding all the M1, ARM, etc targets...
I'm tempted to just skip most of the native targets and just run one for darwin and one for linux. But that's slightly defeating the point of having the CI catch bugs in other platforms
j
if money is not a problem, you can have more macos machines
compiling and running test for each native target
all in parallel
m
💸
Yep, I guess that's an option. It's underoptimal though because we have a Gradle plugin that is going to be compiled several times for each native target
a
It might also be worth getting some attention on this: https://youtrack.jetbrains.com/issue/KT-49385 Even if you're willing to pay for a beefy multi-core macOS machine, Kotlin/Native just doesn't use those extra cores to compile in parallel 😞
👍 3