On 30 May 2012, at 14:58, Sanne Grinovero wrote:


I see two issues with your plan, though:
1. Buildhive is limited to 15 mins, and a reviewer wouldn't
necessarily wait for 2 hours to integrate a pull request anyway. So
the sequential build would be limited to Jenkins runs.
2. How do we select which tests run where? I remember we had to
disable tests precisely because configuring test groups in
testng/surefire didn't work.

I wouldn't oppose a good plan just because of some minor technical
difficulties. We can solve those in many ways.
# improve Arquillian

Yup.

# make-your-own BuildHive by using same integration / have them lift
limitations. (i.e. trust Galder and give him some time..)

Yup.  Galder is working with CloudBees to lift this restriction.  We could also always ping our friends at OpenShift.

# fix/workaround TestNG / switch to JUnit / make your own

Test groups do work, just overriding them on the command line was flaky.  The correct approach is to use Maven profiles.  Solution: fix Maven POMs.

--
Manik Surtani
manik@jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org