Failed to deploy artifacts: Could not transfer artifact 409 error

[Isaac Su]

Hello,

First time publishing a plugin here. I'm getting stuck on an error and not sure how to proceed. Hopefully someone can help.

I have configured the plugin for CD and enabled CD for the plugin.

When I go to run the maven-cd → release job, I get the following error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.4:deploy (default-deploy) on project buildkite: Failed to deploy artifacts: Could not transfer artifact io.jenkins.plugins:buildkite:pom:999999-20250807.010300-1 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): status code: 409, reason phrase: (409) -> [Help 1]

Have I missed a step somewhere? Thanks in advanced for your help.

Cheers,

Isaac Su

[Winter, Markus]

You have a  successful release in run https://github.com/jenkinsci/buildkite-plugin/actions/runs/16796638655

So all is good. The first run was probably too early after CD was enabled. It might take a while after enabling CD until the required secrets are populated to the repo.

---

From: 'Isaac Su' via Jenkins Developers <jenkin...@googlegroups.com>
Sent: Thursday, August 7, 2025 6:31 AM
To: Jenkins Developers <jenkin...@googlegroups.com>
Subject: Failed to deploy artifacts: Could not transfer artifact 409 error

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/7815fe35-236e-4fd1-b241-3be2fcc1a351n%40googlegroups.com.

[Tony Noble]

409 is 'conflict'

Sadly maven doesn't propagate the full error message, but in Artifactory terms, 409 usually means one of:

- The artifact/version already exists in a repository where immutability is set (quite likely for releases)

- Artifactory is detecting that the group and id of the artifact being deployed does not match the group/id location it is being deployed to (and enforcement is enabled)

[Isaac Su]

Thank you all for chiming in.

Turns out the release was failing because I mistakenly placed extensions.xml in <root>/.mvn/.mvn/extensions.xml rather than <root>/.mvn/extensions.xml 🤦

Merging this pull request resulted in the successful release.

Many thanks to Valentin for kindly pointing it out to me.

[Daniel Beck]

On Thu, Aug 7, 2025 at 3:16 PM Tony Noble <tony....@gmail.com> wrote:

409 is 'conflict'

Sadly maven doesn't propagate the full error message, but in Artifactory terms, 409 usually means one of:

- The artifact/version already exists in a repository where immutability is set (quite likely for releases)

- Artifactory is detecting that the group and id of the artifact being deployed does not match the group/id location it is being deployed to (and enforcement is enabled)

For posterity:

In my experience it usually means that you try to deploy a snapshot to a repo only accepting releases. Running `mvn validate help:evaluate -Dexpression=project.version -Dset.changelist -Dignore.dirt` would tell you in that case whether the version looks as expected.

[Tony Noble]

Good point - I missed that scenario.  And the artifact name (artifact io.jenkins.plugins:buildkite:pom:999999-20250807.010300-1) suggests that's exactly what happened here.  

Might be worth checking the distribution management section of the pom.xml for the project.

--

You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKwFG%2BdUYzLffK4_kwDfeHdVr8-cePu4hVsYoaOMrQXXw%40mail.gmail.com.