Other CI Systems

Any CI system that supports environment variables can run Develocity-instrumented builds and publish a Build Scan.
Prerequisites

  • The Develocity plugin or extension is configured in your build. See the documentation for Gradle, Maven, sbt, npm, or Python.

  • You have a Develocity server URL and access key.

Set the Access Key

Expose your Develocity access key as a secret environment variable named DEVELOCITY_ACCESS_KEY in your CI system. Consult your CI system’s documentation for how to store and expose secret values securely.

The access key value uses the format «server host name»=«access key»:

develocity.example.com=7w5kbqqjea4vonghohvuyra5bnvszop4asbqee3m3sm6dbjdudtq

The plugin reads DEVELOCITY_ACCESS_KEY at build time and uses it to authenticate with your Develocity server.

Configure the Server URL for Gradle

With Gradle 9.5.0 or later, you can instrument builds without adding the Develocity plugin to your project’s settings.gradle. In that case, configure the Develocity server URL via the COM_GRADLE_DEVELOCITY_URL environment variable:

COM_GRADLE_DEVELOCITY_URL=https://develocity.example.com

For standard Gradle plugin setups, configure the server URL in settings.gradle instead. For Maven builds, configure the server URL in .mvn/develocity.xml. For other build tools, refer to the relevant plugin documentation.

Verify the Integration

After your first CI run, open your Develocity server and navigate to Build Scan. Your build should appear there. Install the Common Custom User Data plugin to tag builds as CI and enrich each Build Scan with the CI system name, Git branch, and commit SHA.