playframework / playframework/.github
Do not run gradle-cache-action if project/repo does not use Gradle
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 5
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
The Gradle Cache always runs, no matter if the project is using Gradle or not:
https://github.com/playframework/play-mailer/actions/runs/14854450285/job/41704377293#step:6:29
Even worse, if there is a problem, like timeout, it can take long time until the actions finishes:
https://github.com/sbt/sbt-web-build-base/actions/runs/15442013973/job/43461980655?pr=76#step:6:29
here it took more than 500 seconds...
Can we somehow skip the Gradle action with and if: ... condition? Not sure what we could use as condition, something like if repo does not contain a file named *.gradle.kts or *.gradle?
@ihostage What do you think?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in .github/workflows/cmd.yml around lines 130-137 and inspect how the Gradle Cache step is invoked. Determine a condition that skips it for repositories without Gradle files while retaining it for repositories that use Gradle; verify the workflow behavior in both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100