Description:
Using promotion plug-in to (re)deploy artifacts as a post build promotion returns 401 (from Nexus Maven repository).

Steps to reproduce:
1. Create a maven2 job build, with clean install goals
2. Add a promotion which will redeploy artifacts upon a successful build (doesn't matter if it's manual or automatic)
3. run the promotion
result:
Return code is: 401
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
at hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:119)
at hudson.maven.reporters.MavenAggregatedArtifactRecord.deploy(MavenAggregatedArtifactRecord.java:79)
at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:109)
at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:124)
at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:103)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)

Now if you perform "redploy artifacts" from link (in build context) - deploy is successful and running the promotion manually after executing a successful "redeploy artifacts" the promotion succeeds - it seems as if the maven settings isn't being read whilst using the promotion

=> This is a major setback all our release mechanism is based on this deploy promotion.

Also see: http://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin?focusedCommentId=45482210#comment-45482210