Concurrency Jenkins unable to push artifacts to staging

Summary

Unable to push artifacts to https://central.sonatype.com/repository/maven-snapshots/

Steps to reproduce

Run this Jenkins job: https://ci.eclipse.org/cu/view/CI%20Builds/job/concurrency_api-build-snapshot/

What is the current bug behavior?

When attempting to push an artifact to the staging repository a 403 response is returned. This started occurring in February so it could be the authentication token was revoked or expired.

What is the expected correct behavior?

The Jenkins system should have an authentication token under ID central that authorizes us to push artifacts to the snapshots repository.

Relevant logs and/or screenshots

Failed to deploy artifacts: Could not transfer artifact jakarta.concurrent:jakarta.concurrent-tck:jar:3.2.0-20260217.160551-1 from/to central (https://central.sonatype.com/repository/maven-snapshots/): status code: 403, reason phrase: Forbidden (403)

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

Unable to push snapshots to Maven Central.