Can't release - Return code is: 401

[Lars Kruse]

Hey:

I'm trying to release our plugin using:

mvn release:prepare release:perform -Dusername=... -Dpassword=...

It seems to work well enough until the point where the release shall
be uploaded:

[INFO] Uploading:
http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jvnet/hudson/plugins/PUCM/0.3.12/PUCM-0.3.12.pom

...

[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy
(default-deploy) on project PUCM: Failed to deploy artifacts: Could
not transfer artifact org.jvnet.hudson.plugins:PUCM:hpi:0.3.12 from/to
maven.jenkins-ci.org
(http://maven.jenkins-ci.org:8081/content/repositories/releases/):
Failed to transfer file:
http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jvnet/hudson/plugins/PUCM/0.3.12/PUCM-0.3.12.hpi.
Return code is: 401 -> [Help 1]

I'm now very familiar with the release goal so my question is:

The PUCM directory doesn't exist on
http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jvnet/hudson/plugins/

Should someone create it for us? or am I supposed to have access to create it?

I'm using my jenkins.org account (lars_kruse) and I've uploaded my
public ssh key (don't even know if that is necessary).

I tried using both maven 3.0.2 and 2.2

We'er stuck!

[farshid]

I could be wrong but for what its worth i was facing the same 401
error while deploying my plugin update. I figured passing -Dusername -
Dpassword doesn't work at all ( or anymore I think )
i added the user/pass under m2/settings.xml
<servers> <server> <id>xyz</id><username>abc</username><password>efg</
password></server></servers>

and make sure the <id> matches what you have in your distribution
management in pom.xml

I tried mvn release:rollback , delete tags and then restart
release:clean :prepare :perform after updating the m2/settings.xml

-Farshid

On Mar 25, 9:12 am, Lars Kruse <l...@praqma.net> wrote:
> Hey:
>
> I'm trying to release our plugin using:
>
> mvn release:prepare release:perform -Dusername=... -Dpassword=...
>
> It seems to work well enough until the point where the release shall
> be uploaded:
>

> [INFO] Uploading:http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jv...

>
> ...
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy
> (default-deploy) on project PUCM: Failed to deploy artifacts: Could
> not transfer artifact org.jvnet.hudson.plugins:PUCM:hpi:0.3.12 from/to
> maven.jenkins-ci.org
> (http://maven.jenkins-ci.org:8081/content/repositories/releases/):

> Failed to transfer file:http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jv....

> Return code is: 401 -> [Help 1]
>
> I'm now very familiar with the release goal so my question is:
>

> The PUCM directory doesn't exist onhttp://maven.jenkins-ci.org:8081/content/repositories/releases/org/jv...

[Tim Payne]

I had a similar problem when I first started using the new system and found two things
- Company firewall blocked access to the 8081 maven site
- The username and password had to be reset to use the "new" one in the new repository system/wiki/git

Once I had sorted those two out, it worked!

Thanks

[Lars Kruse]

Thanks both Tim and Farshid.

I'll try that out.

Have a nice week-end
lars