commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benedikt Ritter <brit...@apache.org>
Subject Re: [LANG] Jenkins Pipeline DSL
Date Mon, 04 Mar 2019 15:52:23 GMT
Am Mo., 4. März 2019 um 10:50 Uhr schrieb sebb <sebbaz@gmail.com>:

> On Mon, 4 Mar 2019 at 09:47, Benedikt Ritter <britter@apache.org> wrote:
> >
> > Am So., 3. März 2019 um 14:57 Uhr schrieb sebb <sebbaz@gmail.com>:
> >
> > > On Sun, 3 Mar 2019 at 13:28, Benedikt Ritter <britter@apache.org>
> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > here is my proposal for a Jenkins Pipeline file for Commons Lang:
> > > > https://github.com/apache/commons-lang/pull/410
> > > > Please review and comment.
> > >
> > > It looks OK to me, but I think we need to see it in action.
> > >
> > > For example, what about notifications for failed builds - is that
> > > maintained in Jenkins or in the pipeline file?
> > >
> >
> > I will add notification. The PLC4X Project has a good example for that:
> > https://github.com/apache/incubator-plc4x/blob/develop/Jenkinsfile
>
> Thanks.
>
> Sending emails looks really long-winded compared with the Jenkins UI.
> Easy to get things wrong; harder to maintain.
>

It's jetzt the groovy representations of what you would otherwise configure
in the UI.
I've pushed email notifications to the PR on GitHub.


>
> >
> > >
> > > > Benedikt
> > > >
> > > > Am Mi., 20. Feb. 2019 um 11:40 Uhr schrieb Benedikt Ritter <
> > > > britter@apache.org>:
> > > >
> > > > > I'm happy about the positive feedback. I'm currently a little bit
> busy
> > > at
> > > > > work. I hope to be able to spike something at the end of next week.
> > > > >
> > > > > Benedikt
> > > > >
> > > > > Am Mo., 18. Feb. 2019 um 20:25 Uhr schrieb Matt Sicker <
> > > boards@gmail.com>:
> > > > >
> > > > >> The DSL allows you to break out into parallel stages or sequential
> > > > >> ones (or both). The log4net Jenkinsfile has an example of building
> > > > >> across multiple agents:
> > > > >>
> > > > >>
> > > > >>
> > >
> https://github.com/apache/logging-log4net/blob/feature/cd-pipeline/Jenkinsfile
> > > > >>
> > > > >> On Mon, 18 Feb 2019 at 12:44, sebb <sebbaz@gmail.com> wrote:
> > > > >> >
> > > > >> > 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 <boards@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
> > > > >> > > <pascalschumacher@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-unsubscribe@commons.apache.org
> > > > >> > > > For additional commands, e-mail:
> dev-help@commons.apache.org
> > > > >> > > >
> > > > >> > >
> > > > >> > >
> > > > >> > > --
> > > > >> > > Matt Sicker <boards@gmail.com>
> > > > >> > >
> > > > >> > >
> > > ---------------------------------------------------------------------
> > > > >> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > > >> > > For additional commands, e-mail: dev-help@commons.apache.org
> > > > >> > >
> > > > >> >
> > > > >> >
> > > ---------------------------------------------------------------------
> > > > >> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > > >> > For additional commands, e-mail: dev-help@commons.apache.org
> > > > >> >
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Matt Sicker <boards@gmail.com>
> > > > >>
> > > > >>
> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > > >> For additional commands, e-mail: dev-help@commons.apache.org
> > > > >>
> > > > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message