yes, on our 100 Git repos [1], 90% should be easy to run on any CI with minimum configuration and resources
then there is Maven core and complex plugins (like Surefire) which are not the same story if someone wants to test other toolings to show some useful feature we don't get in our current ASF Jenkins configuration [2], just start with some examples of the base 90% and make a demo of something that would be useful to add to our configuration Regards, Hervé [1] https://maven.apache.org/scm.html#Maven_Sources_Overview [2] https://github.com/apache/maven-jenkins-lib Le mercredi 2 janvier 2019, 15:38:12 CET Enrico Olivelli a écrit : > Il giorno mer 2 gen 2019 alle ore 15:34 Vladimir Sitnikov > > <sitnikov.vladi...@gmail.com> ha scritto: > > Enrico> For instance maven-surefire > > integration tests take 2 hours. > > In general I see Travis (free edition) does not offer many resources. > > > > Each Travis job is limited by 50 minutes, however one can split tests into > > multiple jobs, so it will run fine. > > I guess it won't be easy. > Maven integration testing is very complex, it's Maven launching Maven > itself. We will need to improve maven-invoker plugin, I don't know if there > is support for something like JUnit categories. > We can run only "unit tests" and this will be a minimal "feedback" for > the contributor. > For simpler plugins, like "checkstyle", I think Travis would be a good > choice, at least I would give it a try > > Enrico > > > Vladimir > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
