Seems worth trying. I suggest start with one project (i.e. Lang) and see how well it works.
I assume there will need to be a once-off change to Jenkins to switch to using the DSL. Note that some components have multiple jobs, e.g. for different OSes and JVMs. Does the DSL support such jobs? Or is that still done through the GUI? S. On Mon, 18 Feb 2019 at 18:05, Matt Sicker <boa...@gmail.com> wrote: > > +1. You could also make a shared library for reuse in commons projects. > > On Sun, 17 Feb 2019 at 14:41, Pascal Schumacher > <pascalschumac...@gmx.net> wrote: > > > > +1 to using a pipeline > > > > Am 17.02.2019 um 18:35 schrieb Benedikt Ritter: > > > Hi all, > > > > > > I feel like maintaining separate build descriptions on Jenkins is a PITA. > > > Any objections against adopting Jenkins Pipeline DSL for Lang? > > > > > > Regards, > > > Benedikt > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > -- > Matt Sicker <boa...@gmail.com> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
