Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop the gradle daemon after the build task during verification #4261

Conversation

kwvanderlinde
Copy link
Collaborator

@kwvanderlinde kwvanderlinde commented Aug 25, 2023

Identify the Bug or Feature request

Fixes #4260

Description of the Change

This just adds the --no-daemon flag to gradle when executing the build task. This way the lock files are released and windows will allow tar to do its job and the cache to be built.

Possible Drawbacks

Should be none.

Documentation Notes

N/A

Release Notes

N/A


This change is Reviewable

We don't need the gradle daemon anyways, so we can run gradle with the `--no-daemon` flag to stop the daemon after
building. This will release the lock files and allow us to cache the gradle files for faster subsequent verification
runs.
@cwisniew cwisniew added this pull request to the merge queue Aug 25, 2023
Merged via the queue into RPTools:develop with commit 7b674db Aug 25, 2023
4 checks passed
@kwvanderlinde kwvanderlinde deleted the maintenance/4260-windows-build-verification-gradle-cache branch August 25, 2023 03:09
@cwisniew cwisniew added bug code-maintenance Adding/editing javadocs, unit tests, formatting. and removed bug labels Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code-maintenance Adding/editing javadocs, unit tests, formatting.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Maintenance]: Github build verification is slow on windows due to gradle files not being cached
2 participants