Closed icorbett closed 3 months ago
`Could you please try the latest release branch as of c15634bb25b7284dc084f38dff4e838048b7feaf ?
Thank you @vlsi, changing the step definition as follows appears to have resolved our issue!
- uses: burrunan/gradle-cache-action@c15634bb25b7284dc084f38dff4e838048b7feaf
name: Run unit tests with caching
env:
GRADLE_CACHE_PUSH: true
GRADLE_CACHE_USERNAME: ${{ secrets.GRADLE_CACHE_USERNAME }}
GRADLE_CACHE_PASSWORD: ${{ secrets.GRADLE_CACHE_PASSWORD }}
with:
# If you have multiple jobs, use distinct job-id in case you want to split caches
# For instance, jobs with different JDK versions can't share caches
# RUNNER_OS is added to job-id automatically
job-id: ${{ github.event.repository.full_name }}-${{ inputs.DD_TARGET }}
# Specifies arguments for Gradle execution
# If arguments is missing or empty, then Gradle is not executed
arguments: ${{ inputs.GRADLE_TASK }} -Pdd-civisibility
# Gradle version to use for execution:
# wrapper (default), current, rc, nightly, release-nightly, or
# versions like 6.6 (see https://services.gradle.org/versions/all)
gradle-version: wrapper
The latest commit '43902ec585926d41a3150c775d70a83943e7e18d' on the 'release' branch results in the following error for our projects:
They continue to work as expected with the previous release commit '3bf23b8dd95e7d2bacf2470132454fe893a178a1'.
Our most common step definition is:
I'm happy to provide any more insight that I can however troubleshooting this further without guidance is not familiar territory for me.