Well Ben and I both work for CloudBees so we have skin in the game On Wednesday, 31 July 2013, Baptiste MATHUS wrote:
> I am personnally not against using a CloudBees JaaS. If Robert just meant > authenticating through Xircles realm, then I guess this'd be great. > > > 2013/7/31 Stephen Connolly <[email protected]> > > We should be able to have a DEV@cloud Jenkins with an OSS bundle and > integrated auth with xircles.codehaus.org (aka the old version of > grandcentral.cloudbees.com)... I'd just need to double check with Ben... > He may be on our internal IRC soon, so I'll ask if it's trivial or a pain > for him to setup delegated auth. > > Or do you want this on "codehaus" servers! > > > On Wednesday, 31 July 2013, Robert Scholte wrote: > > Hi Baptiste, > > not sure why you think that we only build with M2.2.1, see > https://bamboo-ci.codehaus.**org/build/admin/edit/**editBuildTasks.action? > **buildKey=MOJO-MAPPASM-JOB1<https://bamboo-ci.codehaus.org/build/admin/edit/editBuildTasks.action?buildKey=MOJO-MAPPASM-JOB1> > This is probably a good example of a lot of combinations of JDKs and Maven > versions, both M2 and M3. > Ben has installed specific versions of Maven for me in he past, so it > shouldn't be too hard to get M3.1 here as well. > > I recently noticed that the aggregator has been disabled because it claims > a lot of diskspace. This is probably caused by local repo's per plugin for > the ITs, so we need think of a way to clean it up afterwards. With Jenkins > we will have the same problem. > > Yes, there's one important downside with bamboo infrastructure: IIRC due > to the agents-setup you can't access the workspace. So you have to do it > with the logging or ask support@ to send you a zip. > I'm only interested in Jenkins if it stays within the Codehaus > infrastructure, i.e. controlled through xircles. > > If you need help with some specific plugins to run with Bamboo, just PM me > with your concrete ideas/questions. > > Robert > > > On Wed, 31 Jul 2013 14:10:25 +0200, Baptiste MATHUS <[email protected]> wrote: > > Hi all, > > I was thinking about the fact that IIUC we currently build in Bamboo only > with one version of Maven (2.2.1). Sure, YMMV, but I remember digging a bit > to see how to change it and I found it was a bit complicated and/or slow > (granted, I don't know bamboo). > > I wonder if using Jenkins it wouln't be a little simpler to handle > multi-aspects testing (*matrix builds*, I'm looking at you). > > We could in fact come up with a quite standard matrix build template for > any plugin @MOJO to test for example different maven versions, different > JDK, or even different parameters values (thinking of extra-enforcer-rules > for examples, where we could test against the differen m-e-p versions quite > easily using a matrix build). > > Maybe we could ask CloudBees to see if they can provide the corresponding > required infra? Or ask for Jenkins@MOJO? > > WDYT? > > Thanks > > 2013/3/22 Stephen Connolly <[email protected]> > > There are things we can do with the RBAC plugin and folders that might > solve those issues... but I need to chat with Ben as to how to delegate > auth for a mojo project jenkins to xircles... > > > On 22 March 2013 12:17, Mirko Friedenhagen <[email protected]>wrote: > > Hello, > > I would like Jenkins better for codehaus as well (I hope I may reuse the > account data from codehaus, jenkins-on-cloudbees e.g. would like to get > insight into public *and* private repositories on github, which makes it a > no-go for me). > > Regards Mirko > -- > Sent from my mobile > On Mar 21, 2013 10:08 AM, "Stephen Connolly" < > [email protected]> wrote: > > Well not suggesting *codehaus* abandon it. Just that we set up a JaaS > for the mojo project > > On Thursday, 21 March 2013, Baptiste MATHUS wrote: > > Sure, I personnally know Jenkins a lot better and sure would be more > comfortable with it. > But I also like > > -- Sent from my phone
