Maven deployment 401 error for sonargraph-integration plugin

[a-zitzewitz]

Service(s)

infra.ci.jenkins.io

Summary

Title: Maven deployment 401 error for sonargraph-integration plugin

Details:

• Plugin: sonargraph-integration
• Username: a_zitzewitz
• Using github action jenkins-infra/jenkins-maven-cd-action@v1.2.0
• Issue: Web login works, Maven deploy gets 401
• Error: Could not transfer artifact to https://repo.jenkins-ci.org/releases/
• Permissions file: https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-sonargraph-integration.yml
• Request: Please verify Maven deployment permissions for user a_zitzewitz

Reproduction steps

Run 'cd' action on branch master for https://github.com/jenkinsci/sonargraph-integration-plugin
I have configured MAVEN_USERNAME as "a_zitzewitz" and MAVEN_PASSWORD as the account password, which works fine for manual login.

[MarkEWaite]

As far as I understand it, the repository secrets that are provided by the continuous delivery process for Jenkins plugins are named MAVEN_TOKEN and MAVEN_USERNAME. They should not be modified by the plugin maintainer. In one of the plugins that I maintain, it looks like this:

By default, the continuous delivery process for Jenkins plugins disallows separate releases by the plugin maintainer. You can read more about exclusive CD in pull request:

• Enable exclusive CD by default repository-permissions-updater#3879

[a-zitzewitz]

I added a pull request to add 'cd' to the permission file for the plugin. I hope that will help...

[dduportal]

PR is jenkins-infra/repository-permissions-updater#4692.

That should solve the problem as the HTTP/401 error indicates that authentication is invalid: there are no user/password provided in HTTP POST requests made by Maven or they are invalid (and refused by Artifactory).

Once the PR will be merged in the repository-permission-updater ("RPU"), it may takes up to 3 hours before the automated credentials are updated in your plugin repository (the "RPU" job runs once every hours and generates a new Artifactory token for each plugin which is valid only a few hours: password should not be used).

[dduportal]

Hello @a-zitzewitz it seems that jenkins-infra/repository-permissions-updater#4692 has merged. The "RPU" job has run which should have delivered the proper credentials.

Let us know if you were able to apply Markus's recommendation from the PR to finalize the CD process?

[a-zitzewitz]

Now it works a bit better, but I cannot release, because on your Jenskins tests are failing. The chmod problem is back, since I had to set Jenkins version to 2.532. The release candidate with the fix could not be resolved by my Maven. This failure, as mentioned before, has nothing to do with our code. It seems the tool installation feature struggles with slow file systems.

I have created a pull request for Jenkins core for a similar problem that will occur on the Windows build once the chmod problem is solved: jenkinsci/jenkins#11216

[a-zitzewitz]

Ok, changed back to the rc 2.532-rc37605.6b_b_2172b_1592, now chmod is fixed, but the rename problem persists. For that to be fixed somebody needs to look at my PR (jenkins#11216).