Why not use a settings.xml in the ${HOME}/.m2 of the user that runs jenkins
and use the native 'mvn clean deploy' instead of 'mvn clean package' (or
whatever you are doing :) ?Have you tried that? I am doing it on my jenkins installation and works as a charm. Of course, as long as you are doing an m2 build :) Regards On Tue, Feb 14, 2012 at 5:54 PM, Jeff <predato...@gmail.com> wrote: > Is it Friday yet? (ugh) > > I had been running Jenkins 1.450 and upgraded today to 1.451 and ended up > just blowing away my configurations and (two) jobs and I'm almost back up. > > The last bit I'm having a problem with is publishing my maven build > artifacts to my repository server. I get a ReasonPhrase:Forbidden message > and I'm quite sure it's because I've not given it the credentials. > > For the life of me, I can't remember or find where to set the credentials!! > > In my job configuration at the bottom in the "Post-build Actions" I've > checked the "Deploy artifacts to Maven repository" option and then entered > the "Repository URL" and "Repository ID". > > I would swear there was a field somewhere add username and password > information for the repository. I can't find it in the global Jenkins > config either. > > Can anyone save me from myself and point me to where I set it the > repository credentials? > > -- > Jeff Vincent > predato...@gmail.com > See my LinkedIn profile at: > http://www.linkedin.com/in/rjeffreyvincent > I ♥ DropBox <http://db.tt/9O6LfBX> !! > > -- Those who do not understand Unix are condemned to reinvent it, poorly. Any sufficiently recent Microsoft OS contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Unix.
