So domi was supposed to be integrating my credentials plugin into his config files provider plugin...
If he did that the way I was suggesting then you could have the user submitting the build select the credentials to use as a build parameter (from a list of global credentials and their own user credentials store) - or picking the best match automatically based on the credentials domains for prompt-free builds - and those credentials would be injected into the settings.xml that are provided to the maven build. That was well over a year ago and domi and I were playing ships in the night on IRC... I haven't see those changes land in his config-file provider plugin, so I can only assume it got pushed off his radar. -Stephen On 22 May 2015 at 08:28, Anders Hammar <and...@hammar.net> wrote: > The issue I've been strungling with is that I would like to use the creds > of the person performing a Maven release when deploying to the Maven repo. > Not possible right now out-of-the-box, as the server creds in settings.xml > (possibly handled by Config File Provider Plugin) is "static". So it will > always be the same user/creds. > At one former customer that forced us to always to the releases from > command line. Snapshot builds were handled by Jenkins though and deployed > to the repo. > The limitation is how the creds are handled within Maven core. And as that > part is not easily replaceable (it's not a component that can be repalced) > a change is required in core. There are a few JIRA tickets around this > (MNG-5615, MNG-5356) and I have looked into it a bit. I even had a > developer work on a solution, which I think she completed, but the more I > dug into it I found more parts in core than needed/should be improved at > the same time. And then I simply ran out of time. > The work that was done by a dev collegue can be found here: > https://github.com/devoteam-se (som changes to core, in a branch, and then > one extension that would be current behavior if I remember correctly) > For a current customer I'm looking at going down an easier, but less > flexible, way where I will create a wagon instead that will use the creds > provided in a some other way than from Maven core (could be env variables > for example). The idea is to use this together with the release builds in > Jenkins where the creds would then be the one of the user triggering the > release build. > > /Anders > > On Fri, May 22, 2015 at 9:07 AM, Dan Tran <dant...@gmail.com> wrote: > > > Thanks Domi > > > > @Thomas, mine still not stat large yet but will grow. However, the > > in-house RelEng seems to crank our new VM slaves very fast. But we also > > looking into puppet too > > > > -Dan > > > > On Thu, May 21, 2015 at 11:32 PM, Thomas Broyer <t.bro...@gmail.com> > > wrote: > > > > > So you have a "large number of Jenkins slaves" and no configuration > > > management system? (Puppet, Chef, Ansible, whatever) Isn't that asking > > for > > > trouble? > > > > > > Le ven. 22 mai 2015 06:31, Dan Tran <dant...@gmail.com> a écrit : > > > > > > > Hi > > > > > > > > As you already know place settings.xml under ~/.m2 with NFS is unsafe > > > > > > > > How do you manage Maven credential for your enterprise build with > large > > > > number jenkins slave > > > > > > > > Thanks > > > > > > > > -Dan > > > > > > > > > >
