Onboard to the OSS Community Develocity Instance

[clayburn]

Onboard to the OSS Community Develocity Instance

This PR adds Develocity Build Scan® and Build Cache support
for this project, publishing to the OSS Community Develocity Instance at
https://community.develocity.cloud under project ID meshtastic.

What this PR adds

• The Develocity Gradle extension/plugin and the Common Custom User Data Gradle
  extension/plugin, applied at the latest released versions.
• settings.gradle.kts pointing the build at https://community.develocity.cloud and
  associating builds with project meshtastic.
• A "Revved up by Develocity" badge in the README linking to the filtered Build Scan list
  for this project's root project name.
• A setup step in each GitHub Actions workflow that runs the build, so CI publishes Build
  Scans automatically using a short-lived access token.

Changes to configuration that already existed

This project already applied com.gradle.develocity 4.5.0, so this PR adapts the existing
setup rather than adding it from scratch. Please review these three points.

1. Build Scans move from scans.gradle.com to community.develocity.cloud. The
   termsOfUseUrl and termsOfUseAgree settings are removed, because they apply only to
   the public scans.gradle.com service. Publishing now happens whenever the build is
   authenticated, instead of on CI only, so local builds also publish once a developer
   provisions a key (see Step 3). The explicit capture { fileFingerprints = true } is
   dropped in favor of the plugin default.
2. The remote Build Cache moves to Develocity. gradle/build-cache.settings.gradle
   keeps its role as the single place cache configuration lives, but its self-hosted
   HttpBuildCache is replaced by remote(develocity.buildCache). The now-unused
   GRADLE_CACHE_URL, GRADLE_CACHE_USERNAME, and GRADLE_CACHE_PASSWORD plumbing is
   removed from the workflows; GRADLE_CACHE_READ_ONLY stays, because it controls the
   Actions-side Gradle home cache, not the remote cache. Pushes to the cache happen only
   from CI runs that have the access key, so pull requests from forks read without
   writing.
3. The access key is wired through the shared composite action.
   .github/actions/gradle-setup gets a new optional develocity_access_key input that it
   forwards to gradle/actions/setup-gradle. All 14 call sites pass
   secrets.DEVELOCITY_ACCESS_KEY, and verify-flatpak.yml (which calls setup-gradle
   directly) passes it too. Every input is optional, so builds without the secret keep
   working.

Step 1 — Get an access key for community.develocity.cloud

Build Scan publishing and Build Cache writes from CI need a Develocity access key.

1. Visit https://community.develocity.cloud.
2. Sign in as the CI service account that the Develocity Solutions team has provisioned
   for your project — that account was shared with you out-of-band when this onboarding
   was set up. The access key inherits that account's project memberships and permissions,
   which is exactly what you want for CI.
3. From the user menu in the top-right, open My settings → Access keys.
4. Click Generate access key, give it a description (e.g. GitHub Actions), and copy
   the generated key. Keep this tab open until you complete Step 2 — the key is only
   shown once.

Step 2 — Set the GitHub Actions secret on this repository

CI uses a repository secret named DEVELOCITY_ACCESS_KEY to authenticate to
community.develocity.cloud.

1. Open this repository on GitHub.

2. Click Settings.

3. In the left sidebar, click Secrets and variables → Actions.

4. Click New repository secret. (If a DEVELOCITY_ACCESS_KEY secret already exists,
   click its Update button instead.)

5. Set Name to:

   DEVELOCITY_ACCESS_KEY
   

6. Set Secret to the value below, replacing PASTE_THE_ACCESS_KEY_FROM_STEP_1_HERE
   with the key you copied in Step 1:

   community.develocity.cloud=PASTE_THE_ACCESS_KEY_FROM_STEP_1_HERE
   

   The community.develocity.cloud= prefix is required — without the host name, the
   access key is silently ignored. This is the most common point of failure when
   onboarding, so please double-check the format.

7. Click Add secret (or Update secret).

Step 3 — Provision an access key for your local builds

Developers building this project locally should provision an access key for
community.develocity.cloud so their Build Scans publish and they get reads
from the remote Build Cache. The Develocity Gradle plugin's
provisionDevelocityAccessKey task does this in a single command — it opens
the browser, asks the developer to confirm, and writes the key to
~/.gradle/develocity/keys.properties automatically.

Before running this command, sign out of community.develocity.cloud in
your browser (or use a private/incognito window) so the access key gets
associated with your personal account, not the CI service account you
signed in as for Step 1.

./gradlew provisionDevelocityAccessKey

Note on the CI run on this PR

This PR was prepared from a fork. Forks can't read your repository's secrets, so the
workflow run on this PR cannot publish to community.develocity.cloud even after you set
the secret in Step 2.

If you want CI verification before merging, push the branch
dv/onboard-oss-community-develocity-instance to a temporary branch on this repo (not
the fork) and re-run the workflow there — it will pick up the secret and publish a Build
Scan.

After merging, every CI run on this repository will publish a Build Scan to
https://community.develocity.cloud. CI runs from forks of this repository will not (forks
don't have access to the secret either), and that's expected.

Summary by CodeRabbit

• Improvements

  • Improved build performance and reliability through streamlined remote caching.
  • Enhanced build scan availability and privacy controls for diagnostics.
  • Updated automated documentation, release, and verification workflows for more consistent builds.

• Documentation

  • Added a Develocity status badge to the README, providing direct access to build scan information.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Gradle now uses Develocity for build scans and remote caching. The shared Gradle setup action accepts an access key, and CI workflows pass the repository secret while removing legacy cache credentials. A Develocity badge was added to the README.

Changes

Develocity integration

Layer / File(s)	Summary
Gradle Develocity configuration settings.gradle.kts, gradle/build-cache.settings.gradle, README.md	Gradle configures Develocity scans and remote caching with CI-aware authentication. The README includes a Develocity badge.
Gradle setup action contract .github/actions/gradle-setup/action.yml	The shared action accepts an optional develocity_access_key input and passes it to gradle/actions/setup-gradle.
Workflow secret propagation .github/workflows/*.yml	Release, check, documentation, scheduled, and Flatpak workflows pass DEVELOCITY_ACCESS_KEY. Legacy Gradle cache secrets and environment exports were removed.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Possibly related PRs

• meshtastic/Meshtastic-Android#6026: Both changes modify Develocity configuration in settings.gradle.kts.
• meshtastic/Meshtastic-Android#6200: Both changes modify remote build-cache configuration in gradle/build-cache.settings.gradle.

Suggested labels: ci, build

Suggested reviewers: jamesarich, vidplace7

🚥 Pre-merge checks | ✅ 6

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: onboarding the project to the OSS Community Develocity Instance.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Sibling Call Sites And Presence Semantics	✅ Passed	The PR changes only Gradle, workflow, README, and settings files; it adds no application field, zero-default, nullable field, or presence check requiring sibling call-site updates.
Tests Prove The Path, Not The End State	✅ Passed	The pull request changes only Gradle and workflow configuration plus README content; no added or changed tests require assessment.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@gradle/build-cache.settings.gradle`:
- Around line 18-32: Update the push assignment inside the remote build cache
configuration to require a trusted CI ref or event, such as main-branch or
merge-queue runs, in addition to CI being set and DEVELOCITY_ACCESS_KEY being
present. Ensure feature-branch and pull-request runs cannot push to the shared
cache, while preserving remote caching and existing local-cache behavior.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 72ef5a1c-e326-4c60-b4b2-95aebce399a6

📥 Commits

Reviewing files that changed from the base of the PR and between fe38339 and ec6c539.

📒 Files selected for processing (10)

• .github/actions/gradle-setup/action.yml
• .github/workflows/docs-deploy.yml
• .github/workflows/docs-release.yml
• .github/workflows/release.yml
• .github/workflows/reusable-check.yml
• .github/workflows/scheduled-baseline.yml
• .github/workflows/verify-flatpak.yml
• README.md
• gradle/build-cache.settings.gradle
• settings.gradle.kts

[jamesarich]

🚀