frzb / coinboot-debirf Goto Github PK

While adding a third coinboot-debirf variant (KERNEL=4.18.0-15-generic SUITE=cosmic) I recognized that the way we deploy the build artifacts as Github releases is driven by a race condition - which is working in fine if there are only two builds in the race - else not.
One of the two jobs will always be the last and so be able to deploy cause the other one has already pushed a git tag.

To deploy a release with more than two variants to build in a reliable fashion we have to decouple building and deploying and to coordinate it in a better way.

Looks like we should have a look into TravisCI stages and do something like that: travis-ci/travis-ci#10230