That's a maven release plugin bug not a Jenkins / m2 release bug You will need to use maven-release-plugin 2.2.2 or later.
See http://jira.codehaus.org/browse/MRELEASE-577 On Jul 16, 3:26 pm, erik petzold <erik.petz...@gmail.com> wrote: > Yes there are maven configurations for the jenkins user. It works when > building a project, for example with "clean deploy". > > But while writing this, I have an idea: we specity the maven global > settings with the gs flag, I think the release plugin is not called > with this. > > Thank you > > 2012/7/16 吴亭 <wutingb...@gmail.com>: > > > > > Jenkins user is not the same user with your user. > > > Pls check the auth for your jenkins user. > > > 2012/7/16 Erik <erik.petz...@gmail.com> > > >> Hi, > > >> I have a Problem with the release plugin and hope you can help. > > >> we have jenkins 1.4.7.2 and release plugin 0.9.1 > >> we also use Subversion and Artifactory. > > >> When I try to do a release build, I get the following error when maven > >> wants to download śome artifacts (for example the > >> maven-release-manager-2.3.2.jar): > > >> Authorization failed: Access denied > > >> In the artifactory logfiles I can see, that "non_authenticated_user" tries > >> to download these artifacts. > > >> I can do normal maven builds in jenkins, then the user in the > >> artifactory-logfiles is "jenkins", as it should be (can download and deploy > >> artifacts). > > >> The maven release plugin works when I call it directly (without jenkins). > > >> Do you have any Idea why the jenkins-user is not used by the > >> release-plugin? > > >> Thank you
