Apache Maven Distribution Tools

Clone this repo:
  1. 6900861 Bump mvnversion from 3.10.0 to 3.10.1 by dependabot[bot] · 5 days ago master
  2. c638249 Bump org.eclipse.jetty:jetty-client from 12.1.14 to 12.1.15 by dependabot[bot] · 8 days ago
  3. 5e6da2c Bump org.codehaus.mojo:animal-sniffer-maven-plugin from 1.29 to 1.29.1 by dependabot[bot] · 8 days ago
  4. b0a9995 Bump org.eclipse.jetty:jetty-http from 12.1.14 to 12.1.15 by dependabot[bot] · 8 days ago
  5. 349e180 Bump org.eclipse.jetty:jetty-server from 12.1.14 to 12.1.15 by dependabot[bot] · 8 days ago

Apache Maven Distribution Tool

Apache License, Version 2.0, January 2004 Jenkins Status

Maven Distribution Tool is a tool executed daily on Maven CI server to produce a report of the different checks done on our releases.

Quick Build

mvn verify site

Configuration

API_TOKEN (currently disabled)

The API_TOKEN environment variable is needed by the two Jenkins reports (list-master-jobs and list-branches), since ci-maven.apache.org doesn't allow anonymous access to its JSON API. It is a Base64-encoded username:apitoken string used for HTTP Basic Authentication.

Everything else (gitbox, maven.apache.org, dist/archive.apache.org, lists.apache.org) is read anonymously. Without the token the two reports skip Jenkins and render a page saying the token is missing.

Generating the Token

  1. Log in to the Apache Jenkins instance.
  2. Click your username in the top-right corner to open your user profile.
  3. Navigate to Security (or go directly to https://ci-maven.apache.org/user/<your-username>/security/).
  4. Under API Token, click Add new Token, give it a name, and click Generate.
  5. Copy the generated token — it will not be shown again.
  6. Press Save to store generated token.

To verify the created token got stored correctly, log out and in again and check if the token is listed on the Security page. If the token did not get stored, hit Terminate all sessions. This will log you out. Then repeat the steps above.

Setting the Environment Variable

Base64-encode your Jenkins username and API token, then export it:

export API_TOKEN=$(echo -n 'your-username:your-api-token' | base64)

You can add this to your shell profile (~/.bashrc, ~/.zshrc, etc.) for persistence.

On Windows, you can use the following CMD command to encode it:

powershell "[convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes(\"your-username:your-api-token\"))"

After encoding store it in your environment variables using the following CMD command:

setx API_TOKEN your-Base64-encoded-token /m

Alternatively, configure the variable through the graphical interface. Navigate to Settings → System → About → Advanced system settings → Environment Variables, or search for Environment Variables using the Windows search bar.

Usage

  • Local build with site reports: mvn verify site — the reports use API_TOKEN to fetch data from Jenkins.
  • Integration tests: mvn failsafe:integration-test — the token is passed to the failsafe plugin via the API_TOKEN environment variable.
  • CI (Jenkins): The token is automatically injected via the withCredentials binding in the Jenkinsfile using the API_TOKEN credential ID.