Configure dependency cache on GitHub Actions

[marcphilipp]

In order to speed up builds on GitHub Actions: https://github.com/marketplace/actions/cache

Jobs

• Linux (uses container: junitteam/build:latest)
• Windows
• Mac OS
• Coverage (uses container: junitteam/build:latest)
• Publish Snapshot Artifacts
• Update Snapshot Documentation

[sormuras]

More directories to cache

• gradle/** which contains testing.gradle.kts and the wrapper

More keys to hash

• buildSrc entries, like Versions.kt and friends

.lock files are ... locked

It's not that easy: https://github.com/junit-team/junit5/runs/305358249#step:9:1

Post job cleanup.
"C:\Program Files\Git\usr\bin\tar.exe" -cz --force-local -f d:/a/_temp/6533d433-2e40-451d-b1b0-3824be622ba3/cache.tgz -C C:/Users/runneradmin/.gradle/caches .
/usr/bin/tar: ./6.0/executionHistory/executionHistory.lock: Read error at byte 0, while reading 38 bytes: Device or resource busy
/usr/bin/tar: ./6.0/fileContent/fileContent.lock: Read error at byte 0, while reading 38 bytes: Device or resource busy
/usr/bin/tar: ./6.0/fileHashes/fileHashes.lock: Read error at byte 0, while reading 38 bytes: Device or resource busy
/usr/bin/tar: ./6.0/generated-gradle-jars/generated-gradle-jars.lock: Read error at byte 0, while reading 38 bytes: Device or resource busy
/usr/bin/tar: ./6.0/javaCompile/javaCompile.lock: Read error at byte 0, while reading 38 bytes: Device or resource busy
/usr/bin/tar: ./jars-3/jars-3.lock: Read error at byte 0, while reading 38 bytes: Device or resource busy
/usr/bin/tar: ./journal-1/journal-1.lock: Read error at byte 0, while reading 38 bytes: Device or resource busy
/usr/bin/tar: ./modules-2/modules-2.lock: Read error at byte 0, while reading 38 bytes: Device or resource busy
/usr/bin/tar: Exiting with failure status due to previous errors
##[warning]The process 'C:\Program Files\Git\usr\bin\tar.exe' failed with exit code 2

[sormuras]

Reverting the changes for the time being.

Reserved for future configuration attempts:

    - name: 'Cache Gradle repository'
      uses: actions/cache@v1
      with:
        path: ~/.gradle/caches
        key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle.kts') }}
        restore-keys: ${{ runner.os }}-gradle-

[sormuras]

https://github.com/junit-team/junit5/runs/306095038#step:9:3 says:

##[warning]Cache size of 1947987186 bytes is over the 400MB limit, not saving cache.

[sormuras]

--no-build-cache might help here.

[marcphilipp]

Let's try caching only ~/.gradle/caches/modules-2/

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. Thank you for your contribution.

[jbduncan]

I never said so before, but I'm in support of this proposed change.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. Thank you for your contribution.

[stale]

This issue has been automatically closed due to inactivity. If you have a good use case for this feature, please feel free to reopen the issue.

[StefMa]

Hey guys,

I just came up with the same issue regarding locking files your had here as well.
For me these locking files were only locked in windows machines.
I fixed it by running Gradle without a daemon.
I think it will also work to stop the daemon (./gradlew --stop) before saving of the cache happen.

Just wanted to let you know this 🙃

[marcphilipp]

We have actually since adopted the official Gradle GitHub Action that also takes care of configuring caching.