Migrate to the OSS Community Develocity Instance - #569
Merged
trask merged 1 commit intoSep 1, 2026
Merged
Conversation
|
|
There was a problem hiding this comment.
Pull request overview
Updates this repository’s Gradle Develocity configuration to migrate from the retiring OpenTelemetry-hosted Develocity instance to the shared OSS Community Develocity instance, keeping Build Scan and remote build cache behavior consistent while switching hosts and scoping data to the OpenTelemetry project.
Changes:
- Point
develocityServertohttps://community.develocity.cloud. - Configure
projectId = "OpenTelemetry"so scans/cache are associated with the correct project on the community instance.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This was referenced Aug 31, 2026
Merged
Merged
trask
approved these changes
Sep 1, 2026
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
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.
Migrate to the OSS Community Develocity Instance
OpenTelemetry's dedicated Develocity instance (
https://develocity.opentelemetry.io) is beingretired in favour of the shared OSS Community Develocity Instance at
https://community.develocity.cloud, which Develocity (Gradle Inc.) runs for OSS projects.
Build Scans and the remote build cache keep working exactly as they do today — only the host
changes, and builds are now associated with the
OpenTelemetryproject on the shared instance.What this PR changes
settings.gradle.kts:develocityServernow points athttps://community.develocity.cloud.settings.gradle.kts: addsprojectId = "OpenTelemetry"so Build Scans and cache entries arescoped to the OpenTelemetry project on the shared instance.
Nothing else changes: the CI workflows already read
DEVELOCITY_ACCESS_KEYfrom secrets, so noworkflow edits are needed. Build Scan publishing, remote cache push, and the
build-scan.txtoutput all behave as before.Action required before/when merging
The
DEVELOCITY_ACCESS_KEYsecret must be updated, because the access key format is<host>=<key>and the host is changing:Access keys for the OpenTelemetry CI service account on
community.develocity.cloudhave beenprovisioned by the Develocity team and shared with the maintainers out of band. If the secret
still carries the
develocity.opentelemetry.io=prefix after this PR merges, the key is silentlyignored: CI builds will publish no Build Scans and will not push to the remote cache.
Because the secret is shared across the OpenTelemetry JVM repositories, the cleanest sequence is
to update the (org-level) secret and merge the per-repository PRs together.
Related PRs
This is part of the OpenTelemetry migration to the Community Instance. Companion PRs:
Questions
Happy to adjust anything here — feel free to ping me on this PR or in the CNCF Slack.