As with the recent release, it is not unusual that builds cannot succeed for specific architectures for various reasons. Thus the pipeline needs to be smarter and/or more flexible. Sometimes - as like the last release - the packages need to be published with all succeeding builds asap since upstream released security fixes.
Normally one build failure should fail all (since usually there's a real issue) for consistency. But for situations like above I'd like that a maintainer can manually approve to continue with the pipeline, uploading only succeeding builds and making a release with them only.
If someone has a good idea, any help appreciated.
As with the recent release, it is not unusual that builds cannot succeed for specific architectures for various reasons. Thus the pipeline needs to be smarter and/or more flexible. Sometimes - as like the last release - the packages need to be published with all succeeding builds asap since upstream released security fixes.
Normally one build failure should fail all (since usually there's a real issue) for consistency. But for situations like above I'd like that a maintainer can manually approve to continue with the pipeline, uploading only succeeding builds and making a release with them only.
If someone has a good idea, any help appreciated.