Migrate to the OSS Community Develocity Instance

[cdsap]

Migrate to the OSS Community Develocity Instance

OpenTelemetry's dedicated Develocity instance (https://develocity.opentelemetry.io) is being
retired 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 OpenTelemetry project on the shared instance.

What this PR changes

• settings.gradle.kts: develocityServer now points at https://community.develocity.cloud.
• settings.gradle.kts: adds projectId = "OpenTelemetry" so Build Scans and cache entries are
  scoped to the OpenTelemetry project on the shared instance.

Nothing else changes: the CI workflows already read DEVELOCITY_ACCESS_KEY from secrets, so no
workflow edits are needed. Build Scan publishing, remote cache push, and the
build-scan.txt output all behave as before.

Action required before/when merging

The DEVELOCITY_ACCESS_KEY secret must be updated, because the access key format is
<host>=<key> and the host is changing:

DEVELOCITY_ACCESS_KEY = community.develocity.cloud=<access-key-for-the-community-instance>

Access keys for the OpenTelemetry CI service account on community.develocity.cloud have been
provisioned 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 silently
ignored: 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:

• Migrate to the OSS Community Develocity Instance opentelemetry-java#8760
• Migrate to the OSS Community Develocity Instance opentelemetry-java-instrumentation#19927
• Migrate to the OSS Community Develocity Instance #3085 ← this PR
• Migrate to the OSS Community Develocity Instance opentelemetry-java-examples#1262
• Migrate to the OSS Community Develocity Instance semantic-conventions-java#569
• Migrate to the OSS Community Develocity Instance opentelemetry-proto-java#279

Questions

Happy to adjust anything here — feel free to ping me on this PR or in the CNCF Slack.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: cdsap / name: Inaki Villar (d4330d6)

[Copilot]

Pull request overview

Updates this repository’s Gradle Develocity configuration to use the shared OSS Community Develocity instance, keeping Build Scans and remote build cache behavior aligned with the prior setup while changing the server host and scoping data to the OpenTelemetry project.

Changes:

• Point Develocity server configuration at https://community.develocity.cloud.
• Set projectId = "OpenTelemetry" so scans/cache entries are scoped to the OpenTelemetry project on the shared instance.

Suppressed comments (1)

settings.gradle.kts:34

• isRemoteBuildCachePushEnabled is currently gated on DEVELOCITY_ACCESS_KEY being non-empty, but the access key format is <host>=<key>. After switching develocityServer to community.develocity.cloud, a still-non-empty but wrong-host key (e.g., still prefixed with the old host) will cause the build to (a) disable the local build cache on main and (b) enable remote cache push even though Develocity will ignore the key for this server. Consider checking that the access key contains an entry for the configured server host and using that boolean consistently for server/projectId, build scans, and remote cache push.

val develocityServer = "https://community.develocity.cloud"
val isCI = System.getenv("CI") != null
val develocityAccessKey = System.getenv("DEVELOCITY_ACCESS_KEY") ?: ""
val isRemoteBuildCachePushEnabled = isCI && develocityAccessKey.isNotEmpty()
val shouldDisableLocalBuildCache =

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.