|
| 1 | +name: Nightly Integration Tests |
| 2 | + |
| 3 | +# The integration tests reach out to CATH, ECOD, RCSB, EBI, UniProt and others. |
| 4 | +# That makes them valuable - they are how we find out that an upstream service |
| 5 | +# has changed a URL, a format or a redirect - but it also makes them unsuitable |
| 6 | +# as a gate on pull requests, because an outage anywhere blocks every |
| 7 | +# contributor. Running them on a schedule keeps the coverage while decoupling it |
| 8 | +# from people's ability to merge. |
| 9 | +on: |
| 10 | + schedule: |
| 11 | + # 03:17 UTC daily. Off the hour deliberately: scheduled jobs that ask for |
| 12 | + # exactly midnight queue behind everybody else's. |
| 13 | + - cron: '17 3 * * *' |
| 14 | + # Also runnable by hand, e.g. to confirm an upstream service is back. |
| 15 | + workflow_dispatch: |
| 16 | + |
| 17 | +permissions: |
| 18 | + contents: read # to fetch code (actions/checkout) |
| 19 | + |
| 20 | +jobs: |
| 21 | + integrationtest: |
| 22 | + runs-on: ubuntu-latest |
| 23 | + # These tests download large files from servers we do not control; the |
| 24 | + # default 6 hour limit is far more than they need and far more than we want |
| 25 | + # to spend if one of them hangs. |
| 26 | + timeout-minutes: 90 |
| 27 | + strategy: |
| 28 | + matrix: |
| 29 | + # One JDK only. The point of this run is to exercise the network paths, |
| 30 | + # not the language level, which the pull request build already covers |
| 31 | + # across 11, 17 and 21. |
| 32 | + java: [21] |
| 33 | + fail-fast: false |
| 34 | + name: Integration tests, JDK ${{ matrix.java }} |
| 35 | + |
| 36 | + steps: |
| 37 | + - uses: actions/checkout@v4 |
| 38 | + - name: Set up JDK |
| 39 | + uses: actions/setup-java@v4 |
| 40 | + with: |
| 41 | + distribution: 'oracle' |
| 42 | + java-version: ${{ matrix.java }} |
| 43 | + - name: Build and run integration tests |
| 44 | + run: mvn verify --no-transfer-progress |
| 45 | + - name: Upload surefire reports |
| 46 | + # Kept on failure so an upstream break can be diagnosed after the fact: |
| 47 | + # GitHub expires run logs after 90 days, and these reports carry the |
| 48 | + # stack traces that say which service misbehaved. |
| 49 | + if: failure() |
| 50 | + uses: actions/upload-artifact@v4 |
| 51 | + with: |
| 52 | + name: surefire-reports |
| 53 | + path: '**/target/surefire-reports/**' |
| 54 | + retention-days: 30 |
0 commit comments