Hi. 2020-07-23 12:38 UTC+02:00, Olivier Lamy <ol...@apache.org>: > Hi > As you know the current Jenkins infra is migrating to another CI server. > The current commons-* builds in the old Jenkins infra have been created > manually and this will be a pain to transfer to the new one and to keep > maintaining manually. > In the Maven project we have plenty of maven-* git repo so we have created > a dedicated Jenkins plugin (which is used by other TLP such netbeans) which > scan the gitbox server to get repo based on regular expression or name > content and create the build reusing the same build file. > And this is done without duplicating the build configuration for every > single git repository.... It's done once and updated for all repos when > this configuration change (no need to touch manually every single git > repository) > Each git repo contains a simple Jenkinsfile saying which jdks to use in > case the component has different needs. > I'm happy to help to duplicate similar configuration for commons. > Just let me know.
+1 How does it work with projects having several Jenkins builds (e.g. one for running SonarQube)? Gilles > > cheers > Olivier > > On Thu, 23 Jul 2020 at 16:39, Stefan Bodewig <bode...@apache.org> wrote: > >> On 2020-07-23, Stefan Bodewig wrote: >> >> > My preference would be for using less of github rather than more. But >> > I'm probably alone with that. >> >> Of course I'm not. Sorry Gilles. :-) >> >> Stefan >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
