Hi, I finished by POC for creating per-module build jobs, starting with
- bundles/extensions/i18n - contrib/extensions/sling-pipes These jobs are generated using the code from https://svn.apache.org/repos/asf/sling/trunk/tooling/jenkins/create_j obs.groovy This code in turn is invoked on Jenkins from a 'seed' job https://builds.apache.org/view/S-Z/view/Sling/job/sling-seed-build/ Given that the code is stored in SVN, it's enough to change the groovy file to change the jobs managed by this seed job. A few notes regarding job creation: - jobs are created and updated as needed - when a job is no longer found in the output it is disabled rather than deleted, to make sure we retain history and are protected from accidents The resulting jobs are now at - https://builds.apache.org/view/S-Z/view/Sling/job/sling-bundles-exten sions-i18n-1.7/ - https://builds.apache.org/view/S-Z/view/Sling/job/sling-bundles-exten sions-i18n-1.8/ - https://builds.apache.org/view/S-Z/view/Sling/job/sling-contrib-exten sions-sling-pipes-1.8/ The i18n job is now excluded from the sling-trunk-1.{7,8} builds, to prevent duplicate deployments and wasted time. All the mechanisms are put into place to migrate to per-module builds for bundles, we just need to decide if we want to go ahead with this and whether we want to tweak the way the new jobs are configured at the moment. Thoughts? Thanks, Robert
