Conversation
- Upgrade com.gradle.enterprise 3.13.1 to com.gradle.develocity 4.3.2
- Upgrade common-custom-user-data-gradle-plugin 1.10 to 2.4.0
- Migrate from gradleEnterprise {} to develocity {} DSL
- Update server URL from ge.apache.org to develocity.apache.org
- Enable remote build cache (read-only for local builds, push on CI)
- GRADLE_ENTERPRISE_ACCESS_KEY → DEVELOCITY_ACCESS_KEY (matches the Develocity plugin rename in settings.gradle) - Replace actions/cache + gradle/wrapper-validation-action with gradle/actions/setup-gradle, which handles both caching and wrapper validation
Revert setup-gradle change, keep GRADLE_ENTERPRISE_ACCESS_KEY → DEVELOCITY_ACCESS_KEY rename only.
clayburn
added a commit
to clayburn/samza
that referenced
this pull request
Sep 17, 2026
…ugins
The ASF migrated its Develocity instance from ge.apache.org to
develocity.apache.org, and the Gradle Enterprise plugin was renamed to
Develocity in 3.17. This migrates Samza to the new server and updates
both plugins to current releases:
com.gradle.enterprise 3.13.1 -> com.gradle.develocity 4.5.1
com.gradle.common-custom-user-data-gradle-plugin 1.10 -> 2.8.0
The DSL changes that accompany the rename:
gradleEnterprise {} -> develocity {}
publishAlways() + publishIfAuthenticated() -> publishing.onlyIf { it.authenticated }
The explicit build scan capture configuration is dropped so that the
default capture configuration applies, matching apache/groovy.
A projectId of "samza" is set so builds are attributed to the Samza
project on the shared ASF instance, matching apache/kafka and
apache/groovy.
The CI workflow exports DEVELOCITY_ACCESS_KEY from the
DEVELOCITY_ACCESS_KEY secret. The plugin no longer reads
GRADLE_ENTERPRISE_ACCESS_KEY, and DEVELOCITY_ACCESS_KEY is the secret
name ASF INFRA provisions for develocity.apache.org.
Remote build cache configuration is unchanged.
Supersedes apache#1714 and apache#1718.
Author
|
Superseded by #1723 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
com.gradle.enterprise3.13.1 →com.gradle.develocity4.3.2com.gradle.common-custom-user-data-gradle-plugin1.10 → 2.4.0gradleEnterprise {}DSL →develocity {}DSLge.apache.orgtodevelocity.apache.orgThe Gradle Enterprise plugin was renamed to Develocity in version 3.17. The old
com.gradle.enterpriseplugin ID andgradleEnterprise {}DSL are deprecated. This aligns Samza with other Apache projects (Kafka, Groovy) that have already migrated.The Develocity plugin 4.3.2 is compatible with Gradle 6.0+ and maintains full backward compatibility with the Samza build.