Loading
ci: build packages in a child pipeline instead of in the main one
Following Alpine's example. This allows some optimizations:
- Don't start one job per architecture simply to skip them after rebase and before merge
- If there are no packages, don't start the jobs at all
- In the future, we can avoid creating jobs for architectures that don't have changed packages, thus further reducing the unnecessary jobs and possibly reducing transient failures
I had been thinking about this for a while, since it always annoyed me that build jobs would be created when I told the pipeline: "skip build". However, what finally triggered this is the last round of edge breaking. Most things I wanted to merge are broken on armv7 or riscv64 repos being broken upstream. But none of those MRs build armv7 or riscv64 things, so those jobs being started and failing do not provide any benefit. That second part is not in this MR, but this MR provides the ground work to make it possible
Edited by Pablo Correa Gomez