Bump org.eclipse.jgit:org.eclipse.jgit

Bumps [org.eclipse.jgit:org.eclipse.jgit](https://github.com/eclipse-jgit/jgit) from 7.7.0.202606012155-r to 7.7.1.202607240634-r.
- [Commits](https://github.com/eclipse-jgit/jgit/compare/v7.7.0.202606012155-r...v7.7.1.202607240634-r)

---
updated-dependencies:
- dependency-name: org.eclipse.jgit:org.eclipse.jgit
  dependency-version: 7.7.1.202607240634-r
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
1 file changed
tree: 621c1572f5ff3980d8311d5bc4f13962996354b2
  1. .github/
  2. .mvn/
  3. src/
  4. .asf.yaml
  5. .gitignore
  6. check-plugins-maven4.sh
  7. Jenkinsfile
  8. LICENSE
  9. NOTICE.txt
  10. pom.xml
  11. README.md
README.md

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

The API_TOKEN environment variable is required to authenticate HTTP requests against the Apache Jenkins instance and other Apache infrastructure. It is a Base64-encoded username:apitoken string used for HTTP Basic Authentication.

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.

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.

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.