[keycloak-dev] Jenkins

Marek Posolda mposolda at redhat.com
Thu Feb 13 05:43:35 EST 2014

I've created job in internal jenkins to build keycloak master: 

This build should be triggered automatically after new PR is merged to 
git at github.com:keycloak/keycloak.git . Currently you can see that build 
is failing due to some errors in references to parent-poms but this 
should be fixed after you merge my PR 
https://github.com/keycloak/keycloak/pull/202 .

You need to be on RH VPN to see the build. If you want to do some 
changes in build configuration or create new build, you will need to 
login into Jenkins (use your RH kerberos credentials). If you have 
access to 
we are fine.

Do you want to trigger job automatically just when PR is merged or also 
when someone send PR? AFAIK Jenkins has support just for the former. We 
have setup the latter in gatein-portal, but that doesn't use RH Jenkins 
but some other CI AFAIK. I can ask Thomas if you want this too, but do 
you think it's needed? IMHO it is quite sufficient to trigger build just 
when PR is merged?

One of the advantages of our jenkins is, that it has support for all 
databases. If you want me to continue, I will try to add more builds. I 
think we need:
- Build for running testsuite with mongo
- Matrix build for run unit tests with all RDBMS
- Matrix build for run testsuite with all RDBMS

When I finish UUID stuff (String Id generated by java.util.UUID instead 
of autogenerated by DB), we will be hopefully fine with all databases 
and won't see more DB related issues.


On 12.2.2014 18:25, Bill Burke wrote:
> 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev

More information about the keycloak-dev mailing list