On Mon, 2016-09-19 at 16:39 +0200, Carsten Ziegeler wrote: > > > > On Mon, 2016-09-19 at 15:53 +0200, Carsten Ziegeler wrote: > > > > > > The benefit of the current solution is clear: below or equal to > > > zero. > > > Afaik, Robert look already into having per module jobs in > > > jenkins. > > > Not > > > sure how far this is. > > > > I pinged infra about this and noone opposed :-) > > > > http://mail-archives.apache.org/mod_mbox/www-builds/201609.mbox/b > > rows > > er > > > > I would be happy to look into per-module builds based on Jenkins. > > I've > > done some work automating similar setups in the past using Job DSL > > plugin > > > > https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin > > > > I can file a request for infra to install this plug-in and start > > testing on a limited set of modules if no one objects. We can then > > gradually migrate modules off the 'main' job and move them to > > individual jobs. > > > Sounds great to me, thanks Robert!
Filed https://issues.apache.org/jira/browse/SLING-6061 https://issues.apache.org/jira/browse/INFRA-12632 Let's see where this takes us :-) Robert
