CVS - Permission denied (publickey,gssapi-with-mic,password)

[OscarMartins]

Hello everyone

You know what's missing so you can do the build?

[David Doughty]

I've got some users who are trying as a post build action to deploy artefacts to Nexus

Using the maven goal deploy the build picks up the settings.xml from the maven install on the build box.

Using the plugin, it appears to be trying to access the user settings.xml (jenkins user in .m2/repository/settings.xml, which doesn't exist).

I've not used the post build action deploy previously, can anyone tell me if this is working as expected, or did I miss a config step to get it to pickup the installation settings.xml?

Currently we're running 1.482 Jenkins on this linux box

Thanks

dD

[David Doughty]

So after a little googling around, this appears to be a repeatable problem, in that the redeploy publisher no longer reverts to the global settings.xml file, which is a pain in the arse. WE can resolve this by copying the settings.xml into .m2, which isn't really a good as a long term solution.

Anyhow, this brings me to the next problem. We get an ERror: ReturnCode 401;unauthorised. The login credentials are in the settings.xml, and the pom has the correct id reference, does anyone have any suggestions? We;re trying to deploy to Nexus, the account in settings.xml exists and password are correct it has group deploy privileges, and as far as I can tell everything joins up.

Any thoughts from the group?

Thanks

dD

From: David Doughty <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Wednesday, 3 October 2012 12:08
To: "[hidden email]" <[hidden email]>
Subject: Maven Post Action Deploy?

I've got some users who are trying as a post build action to deploy artefacts to Nexus

Using the maven goal deploy the build picks up the settings.xml from the maven install on the build box.

Using the plugin, it appears to be trying to access the user settings.xml (jenkins user in .m2/repository/settings.xml, which doesn't exist).

I've not used the post build action deploy previously, can anyone tell me if this is working as expected, or did I miss a config step to get it to pickup the installation settings.xml?

Currently we're running 1.482 Jenkins on this linux box

Thanks

dD