How it works? I mean if matrix is built on the fly, schedule is inside matrix, right? How github can have prior knowledge when to run scheduled jobs then
On Fri, Nov 20, 2020, 4:16 AM Tim Duesterhus <t...@bastelstu.be> wrote: > Willy, > Ilya, > > find two patches improving the CI. > > 1) This lays the foundation to check the workflow trigger in the matrix > generator Python script, allowing us to move less important jobs into > a daily / weekly schedule. > > 2) This cleans up the Windows CI. I've made sure to re-use as much as > possible > from the VTest workflow, like I did for the compliance one. > > You can find the example output here: > > https://github.com/TimWolla/haproxy/runs/1427467730?check_suite_focus=true > > Best regards > > Tim Düsterhus (2): > CI: Pass the github.event_name to matrix.py > CI: Clean up Windows CI > > .github/matrix.py | 9 +++++ > .github/workflows/vtest.yml | 2 +- > .github/workflows/windows-latest.yml | 20 ---------- > .github/workflows/windows.yml | 60 ++++++++++++++++++++++++++++ > 4 files changed, 70 insertions(+), 21 deletions(-) > delete mode 100644 .github/workflows/windows-latest.yml > create mode 100644 .github/workflows/windows.yml > > -- > 2.29.0 > >
