Skip to content

GitHub runners: Make sure to start any Gradle build runs with a unique cache key. At least for master merges, to ensure bits are clean and deterministic #220

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.

Sign up for GitHub

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

Jump to bottom
Open
lagergren opened this issue May 9, 2024 · 0 comments
Open

GitHub runners: Make sure to start any Gradle build runs with a unique cache key. At least for master merges, to ensure bits are clean and deterministic #220

lagergren opened this issue May 9, 2024 · 0 comments
Assignees
@lagergren

Comments

@lagergren
Copy link
Contributor

Caching is very conservative atm, so it shouldn't be a problem, and no one else can write to the master cache for its build actions, but better safe than sorry.
@lagergren lagergren self-assigned this May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lagergren lagergren

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lagergren