Now that we have 2 ASF Organization Jenkins jobs (one for gitbox [1] and one for git-wip: thank you Stephen) and that it looks quite successful, let's plan the next steps.
Here is what I see: 1. removal of hand-defined Jenkins jobs that are now duplicates 2. preparation of the 60 new empty git repos for shared & plugins 3. migration of the 1 shared component and 1 plugin using migrate-*.sh scripts [3] to test and eventually rework the Jenkinsfile (I suppose it will require some little change, to run add "run-its" profile) For the plugin, I'd like to do the job for maven-site-plugin, since we expect to release it soon. For the shared component, I don't know if there is a best candidate 4. once previous step is ok, do the full migration: if there are volunteers for helping, that would be great, since populating 60 git repos won't be really fun... And as part of 60 empty git repos creation, I propose to migrate the "Google repo manifest" maven-aggregator [4] to ASF: my personal use has been quite successful, I hope it's the same for others. Perhaps there are better ideas for its name: maven-aggregator Any other idea? any objection? Regards, Hervé [1] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/ [2] https://builds.apache.org/view/M-R/view/Maven/job/maven-wip/ [3] https://svn.apache.org/viewvc/maven/sandbox/trunk/scripts/git/ [4] https://github.com/hboutemy/maven-aggregator --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
