Skip to content

Jenkins ee4j.data cannot publish snapshots

Summary

The Jenkins instance https://ci.eclipse.org/data/ is configured with an outdated settings.xml after the migration from OSSRH to Central publishing.

Steps to reproduce

Attempt to run the job Jakarta Data Deploy here: https://ci.eclipse.org/data/job/jakarta-data-deploy/

What is the current bug behavior?

All the artifacts are correctly built and we are using the org.sonatype.central:central-publishing-maven-plugin:0.8.0 plugin. When it comes time to publish we get the following warning:

[ERROR] Failed to execute goal org.sonatype.central:central-publishing-maven-plugin:0.8.0:publish (injected-central-publishing) on project jakarta.data-tck-dist: Failed to deploy artifacts: Could not transfer artifact jakarta.data:jakarta.data-api:json.asc:cyclonedx:1.1.0-20250915.192951-1 from/to central-snapshot (https://central.sonatype.com/repository/maven-snapshots/): status code: 401, reason phrase: Unauthorized (401)

Which suggests that the settings.xml present on the Jenkins system has not been updated with the correct credentials to be able to push artifacts to the snapshot repository.

What is the expected correct behavior?

The Jenkins build should be able to push artifacts to the snapshot repository.

Relevant logs and/or screenshots

https://ci.eclipse.org/data/job/jakarta-data-deploy/417/console

Priority

  • Urgent
  • High
  • Medium
  • Low

Severity

  • Blocker
  • Major
  • Normal
  • Low

Impact

This is blocking the ability for implementations of the Jakarta Data API from consuming SNAPSHOTS and effectively slowing down development of the 1.1.0 version.