Anonymous Access

Configure the level of access granted to users who are not logged in to Develocity.

Anonymous access allows developers to publish builds without per-user authentication, simplifying setup. Weigh that convenience against your security and data privacy requirements.

Understanding Anonymous Access

By default, Develocity allows anonymous users to view and create Build Scan data. This allows developers to publish and analyze builds without authenticating.

The built-in Build Cache node denies anonymous access by default. Users must authenticate to use the cache unless you change this in the service settings.

Configure via the User Interface

To modify anonymous permissions in the Develocity UI:

  1. Log in to Develocity as a user with the Administrator role.

  2. Navigate to Administration  Access control  Anonymous access.

  3. Select the access level or the specific permissions to grant unauthenticated users.

  4. Click Save to store the settings.

  5. Click Apply and restart in the upper-right corner to activate them.

Applying configuration can take several minutes.
Anonymous Access Configuration in Develocity UI
Anonymous Access Configuration in Develocity UI

Configure via Unattended Configuration

If you are managing Develocity using a GitOps or automated workflow, you can define the global settings using Unattended Configuration. Depending on your deployment strategy, you can provide these settings either as Integrated configuration within your values.yaml or as a Standalone configuration file.

version: 17
systemPassword: "«hashed-system-password»"
auth:
  anonymousPermissions:
    - viewScan
    - publishScan
  external: null
  projects:
    acceptAnonymousProjects: true
    enabled: false

Deployment Templates

Download the appropriate YAML template to begin your infrastructure configuration.

For Develocity versions 2025.3 and prior, see the 2025.2 Administration Guide or the 2025.3 Administration Manual.

Cluster Deployment

Example template for cluster orchestration.
gradle-enterprise-config-schema-17.yaml | SHA256 | ASC | ASC SHA256
Standalone Deployment

Example template for standalone setup.
gradle-standalone-config-schema-17.yaml | SHA256 | ASC | ASC SHA256

Pre-deployment Checklist

  • Backup: Export your current settings via Administration  Import/export before applying changes.

  • Deployment: After updating your values.yaml, re-deploy using Helm.

  • Impact: This triggers service restarts and may take several minutes to complete.

See Unattended Configuration for details.

Security Considerations

  • Data Exposure: Enabling VIEW_BUILD_SCANS anonymously means anyone with network access to Develocity can see project names, dependency versions, and environment variables included in scans.