Hi all, at the summit I am attending, there are a large number of folks
from the TravisCI team. They indicated they would be happy for any feedback
about pain points anyone in the Groovy community (or more generally the JDK
community) have when running your Groovy/JDK related CI builds with
TravisC
Hi Paul,
The max timeout(about 50 minutes) of buiding is too short for big
projects to complete tons of tests. Apache Groovy[1]'s test building costs
about 25 minutes, and groovy-parser project[2]'s building costs more than 50
minutes when running on Travis CI as it will test parsing source
