Skip to content

ci: restrict Develocity cache writes to trusted events #37

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

Merged
jamesarich merged 1 commit into from
Aug 3, 2026
Merged

ci: restrict Develocity cache writes to trusted events #37

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions gradle/develocity.settings.gradle
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,13 @@ buildCache {
}
remote(develocityBuildCache) {
enabled = true
// Only authenticated CI writes, so unmerged and fork code cannot poison the cache.
push = isCI && accessKey != null && !accessKey.isEmpty()
// Write only from trusted events. Local dev is excluded by isCI, and
// pull_request runs are excluded here: a same-repository PR DOES receive
// repository secrets, so gating on the access key alone would let
// unmerged code write entries into the shared cache. Fork PRs have no
// key and are excluded twice over.
def eventName = System.getenv("GITHUB_EVENT_NAME")
def trustedForPush = eventName == "push" || eventName == "merge_group"
push = isCI && trustedForPush && accessKey != null && !accessKey.isEmpty()
}
}