generally, there was an idea of keeping "developer velocity" as high as possible. i.e. to perform check in 3-5 min after the push.
Github Actions allows 4 parallel builds (same as Travis CI), I thought of moving some builds to GH actions. also, that was a reason to move some rare configurations to "cron" trigger. Big matrix takes 30 min. It is not acceptable. ср, 29 июл. 2020 г. в 21:53, Tim Düsterhus <t...@bastelstu.be>: > Ilya, > List, > > Am 29.07.20 um 18:49 schrieb Tim Duesterhus: > > [long snip] > > You can find an example run of that GitHub Action workflow here: > > https://github.com/TimWolla/haproxy/actions/runs/187396816 > > I've attached a screenshot of how nice it looks in the commit overview > compared to Travis. > > The build output itself also is much cleaner, because it clearly > separates the steps and even allows to collapse substeps (e.g. the ldd > output): > > https://github.com/TimWolla/haproxy/runs/924096838?check_suite_focus=true > > Ilya, feel free to adjust around in that workflow file. But please take > care to keep it as clean as possible. I hope that the Python support > helps here. The Travis one is a small mess to be honest :-) > > Best regards > Tim Düsterhus >
