To make sure Keycloak works on different containers (EAP, WildFly, others?), multiple databases (MySQL, PostgreSQL, Mongo, others?) and that I don't break the build it would be great to have Jenkins setup to run tests for us. Question is, do we rely on internal Jenkins servers (tickets, vpn, etc.) or do we use CloudBees? My personal preference is CloudBees, but if there is strong objections I don't mind either way. Marek has experience with Jenkins so he's kindly volunteered to set this up for us (right?) ;) _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev

marek now how to integrate it with PRs? On 2/12/2014 10:50 AM, Stian Thorgersen wrote: > To make sure Keycloak works on different containers (EAP, WildFly, others?), multiple databases (MySQL, PostgreSQL, Mongo, others?) and that I don't break the build it would be great to have Jenkins setup to run tests for us. > > Question is, do we rely on internal Jenkins servers (tickets, vpn, etc.) or do we use CloudBees? My personal preference is CloudBees, but if there is strong objections I don't mind either way. > > Marek has experience with Jenkins so he's kindly volunteered to set this up for us (right?) ;) > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/keycloak-dev >

On 2/13/2014 5:43 AM, Marek Posolda wrote: > Do you want to trigger job automatically just when PR is merged or also > when someone send PR? In WildFly we kick off a build and test for each PR sent. If it is not successful it doesn't get merged. That saves us a ton of headache. I can't remember the last time the build was broken. It just practically never happens any more. I think Keycloak will soon enter a phase where it gets lots of contributors submitting PR's. The sooner you force a successful build and test BEFORE a merge the better.

----- Original Message ----- > From: "Bill Burke" <bburke(a)redhat.com&gt; > To: keycloak-dev(a)lists.jboss.org > Sent: Thursday, 13 February, 2014 2:29:06 PM > Subject: Re: [keycloak-dev] Jenkins > > > > On 2/13/2014 9:26 AM, ssilvert(a)redhat.com wrote: >> On 2/13/2014 5:43 AM, Marek Posolda wrote: >>> Do you want to trigger job automatically just when PR is merged or also >>> when someone send PR? >> In WildFly we kick off a build and test for each PR sent. If it is not >> successful it doesn't get merged. That saves us a ton of headache. I >> can't remember the last time the build was broken. It just practically >> never happens any more. >> >> I think Keycloak will soon enter a phase where it gets lots of >> contributors submitting PR's. The sooner you force a successful build >> and test BEFORE a merge the better. >> > > +1. +10 (one point for every time I've broken the build!)

----- Original Message ----- > From: "Bill Burke" <bburke(a)redhat.com&gt; > To: "Stian Thorgersen" <stian(a)redhat.com&gt; > Cc: keycloak-dev(a)lists.jboss.org > Sent: Thursday, 13 February, 2014 2:57:32 PM > Subject: Re: [keycloak-dev] Jenkins > > > > On 2/13/2014 9:49 AM, Stian Thorgersen wrote: >> >> >> ----- Original Message ----- >>> From: "Bill Burke" <bburke(a)redhat.com&gt; >>> To: keycloak-dev(a)lists.jboss.org >>> Sent: Thursday, 13 February, 2014 2:29:06 PM >>> Subject: Re: [keycloak-dev] Jenkins >>> >>> >>> >>> On 2/13/2014 9:26 AM, ssilvert(a)redhat.com wrote: >>>> On 2/13/2014 5:43 AM, Marek Posolda wrote: >>>>> Do you want to trigger job automatically just when PR is merged or also >>>>> when someone send PR? >>>> In WildFly we kick off a build and test for each PR sent. If it is not >>>> successful it doesn't get merged. That saves us a ton of headache. I >>>> can't remember the last time the build was broken. It just practically >>>> never happens any more. >>>> >>>> I think Keycloak will soon enter a phase where it gets lots of >>>> contributors submitting PR's. The sooner you force a successful build >>>> and test BEFORE a merge the better. >>>> >>> >>> +1. >> >> +10 (one point for every time I've broken the build!) >> > > I don't know if you remember Iona? An Irish CORBA company. When > somebody broke the build you had to buy everybody on team a Guiness. On > our team page, your name had a Guiness pint jpg for each time you broke > the build. That would be very expensive in shipping costs :( Luckily CORBA was before my days, but Arjuna had loads of Iona boxes ;)