...
We have a few agregator trees that have to be split in a collection of git repos.
For For each aggregator, there are currently a few Jenkins jobs (corresponding to misc Maven or JDK versions) that will require to be split too. Sonar configuration will require rework too.
And general question: how to clone/update such a collection of git repos (to avoid working on each repo individually)?
No strategy currently found on these 3 topics.
| aggregator | content | Jenkins | Sonar |
|---|---|---|---|
| plugins | 1 parent pom + 41 plugins | 10 aggregator jobs: maven-plugin maven-plugins-ITs-m2 maven-plugins-ITs-m2-with-maven-plugin maven-plugins-ITs-m3 maven-plugins-ITs-m3-windows maven-plugins-ITs-m3.0.4 maven-plugins-ITs-m3.0.5-with-maven-plugin maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8 maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8_windows maven-plugins-windows | Apache Maven Plugins Aggregator |
| pom | 2 parent poms without aggregator | 2 jobs: maven-parent ASF Parent Pom | N/A |
| resources | 1 parent pom + 6 resources | 1 aggregator job: maven-project-resources | N/A |
| shared | 1 parent pom + 26 shared components | 2 aggregator jobs: maven-shared maven-shared-windows | Maven Shared Components Aggregator |
| skins | 1 parent pom + 5 skins | 1 aggregator job: maven-skins | N/A |
| doxia-tools | 1 parent pom + 5 tools | 1 aggregator job: doxia-tools | Doxia Aggregator |
...
| archetypes |
Migration process description
...