Killer. Nice work.
> On Mar 23, 2019, at 8:58 AM, Benedikt Ritter wrote:
>
> Hi!
>
> the PR has been merged and I've created a multi branch pipeline [1]. I've
> used the configuration from the PLC4X project because I know they were
> among the first to use pipeline files. I recommend that we le
Hi!
the PR has been merged and I've created a multi branch pipeline [1]. I've
used the configuration from the PLC4X project because I know they were
among the first to use pipeline files. I recommend that we let this build
for a while to get a feeling whether this works the way we want. If it does
On Mon, Mar 4, 2019 at 03:46, Benedikt Ritter wrote:
> Am Mo., 4. März 2019 um 00:17 Uhr schrieb Matt Sicker :
>
> > I think you can combine the analysis steps into one mvn command.
> >
>
> Makes sense. What I really want to have is all the analyze steps running in
> parallel. Is that passible?
>
Am Mo., 4. März 2019 um 10:50 Uhr schrieb sebb :
> On Mon, 4 Mar 2019 at 09:47, Benedikt Ritter wrote:
> >
> > Am So., 3. März 2019 um 14:57 Uhr schrieb sebb :
> >
> > > On Sun, 3 Mar 2019 at 13:28, Benedikt Ritter
> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > here is my proposal for a Jenkin
On Mon, 4 Mar 2019 at 09:47, Benedikt Ritter wrote:
>
> Am So., 3. März 2019 um 14:57 Uhr schrieb sebb :
>
> > On Sun, 3 Mar 2019 at 13:28, Benedikt Ritter wrote:
> > >
> > > Hi all,
> > >
> > > here is my proposal for a Jenkins Pipeline file for Commons Lang:
> > > https://github.com/apache/comm
Am So., 3. März 2019 um 14:57 Uhr schrieb sebb :
> On Sun, 3 Mar 2019 at 13:28, Benedikt Ritter 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
Am Mo., 4. März 2019 um 00:17 Uhr schrieb Matt Sicker :
> I think you can combine the analysis steps into one mvn command.
>
Makes sense. What I really want to have is all the analyze steps running in
parallel. Is that passible?
>
> On Sun, 3 Mar 2019 at 14:15, Pascal Schumacher
> wrote:
> >
>
I think you can combine the analysis steps into one mvn command.
On Sun, 3 Mar 2019 at 14:15, Pascal Schumacher wrote:
>
> Am 03.03.2019 um 14:56 schrieb sebb:
> > For example, what about notifications for failed builds - is that
> > maintained in Jenkins or in the pipeline file?
>
> Notification
Am 03.03.2019 um 14:56 schrieb sebb:
For example, what about notifications for failed builds - is that
maintained in Jenkins or in the pipeline file?
Notification can be defined in the pipeline.
Pretty much everything can be defined in a jenkins file nowadays (some
plugins do not have pipelin
On Sun, 3 Mar 2019 at 13:28, Benedikt Ritter 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
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.
Benedikt
Am Mi., 20. Feb. 2019 um 11:40 Uhr schrieb Benedikt Ritter <
brit...@apache.org>:
> I'm happy about the positive feedback. I'm currently
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 :
> The DSL allows you to break out into parallel stages or sequential
> ones (or both). T
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 wrote:
>
> Seems worth t
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 i
+1. You could also make a shared library for reuse in commons projects.
On Sun, 17 Feb 2019 at 14:41, Pascal Schumacher
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 PIT
+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
Am So., 17. Feb. 2019 um 19:48 Uhr schrieb Gary Gregory <
garydgreg...@gmail.com>:
> This will be versioned in the repo just like we do for Travis?
>
Yes. It's a description of a jenkins job in a groovy DSL, see
https://jenkins.io/solutions/pipeline/
>
> Gary
>
> On Sun, Feb 17, 2019, 12:36 Ben
None from me. +1
Sent from Yahoo Mail on Android
On Mon, 18 Feb 2019 at 6:36, Benedikt Ritter wrote: 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
This will be versioned in the repo just like we do for Travis?
Gary
On Sun, Feb 17, 2019, 12:36 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
>
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
20 matches
Mail list logo
