From 35014727f78f5c494a745ee3b6f3192ed0457ba6 Mon Sep 17 00:00:00 2001 From: Jay Berkenbilt Date: Wed, 21 Oct 2020 14:07:49 -0400 Subject: [PATCH] Build on a schedule and use latest versions of runners --- .github/workflows/main.yml | 10 ++++++++-- TODO | 6 ------ 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 441e5b23..ed963ef1 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -13,6 +13,12 @@ on: - 'README*' - 'TODO' pull_request: + schedule: + # Building regularly with cron makes it safe for us to use + # *-latest with runs-on. If a new version of tools or agents comes + # out, we'll find out fast if our builds break on it because we + # have reliable testing. + - cron: '12 4 * * 5' jobs: Distfiles: # Generate distfiles.zip, which is a prerequisite for the mac and @@ -41,7 +47,7 @@ jobs: name: distribution path: distribution Windows: - runs-on: windows-2019 + runs-on: windows-latest needs: Distfiles strategy: fail-fast: false @@ -67,7 +73,7 @@ jobs: name: distribution path: distribution macOS: - runs-on: macos-10.15 + runs-on: macos-latest needs: Distfiles steps: - uses: actions/checkout@v2 diff --git a/TODO b/TODO index f0d5f8a4..afc5796a 100644 --- a/TODO +++ b/TODO @@ -3,8 +3,6 @@ Candidates for upcoming release * Easy build/test * #460: potential malware in fuzzer seed corpus - * Consider building workflow on a schedule to detect build rot. This - should enable safe use of *-latest on runners. * Fuzz crashes * See "New" below @@ -24,10 +22,6 @@ Candidates for upcoming release * Complete migration. Do a case-insensitive search for azure to find documentation references. - * Build qpdf weekly so we can notice if things start breaking - because of changes in the build environment, library dependencies, - compiler upgrades, etc. - * See if we can work in Windows Build/External Libraries (below) * Remember to check work `qpdf` project for private issues