Re: Configuring Jenkins

2016-11-16 Thread Vikas Kedigehalli
This is awesome! Looking forward to separate builds for java and python for faster builds! On Tue, Nov 15, 2016 at 9:59 AM, Kenneth Knowles wrote: > Awesome. This is a dramatic improvement. > > On Tue, Nov 15, 2016 at 8:52 AM, Amit Sela wrote: > > > Sweet! Versioning changes in a visible way ca

Re: Configuring Jenkins

2016-11-15 Thread Kenneth Knowles
Awesome. This is a dramatic improvement. On Tue, Nov 15, 2016 at 8:52 AM, Amit Sela wrote: > Sweet! Versioning changes in a visible way can save a lot of pain.. > > Thanks Davor! > > On Tue, Nov 15, 2016, 18:47 Robert Bradshaw > wrote: > > > This is great; thanks for doing this! > > > > On Tue,

Re: Configuring Jenkins

2016-11-15 Thread Amit Sela
Sweet! Versioning changes in a visible way can save a lot of pain.. Thanks Davor! On Tue, Nov 15, 2016, 18:47 Robert Bradshaw wrote: > This is great; thanks for doing this! > > On Tue, Nov 15, 2016 at 6:43 AM, Dan Halperin > wrote: > > Seems phenomenal! > > > > Reading between the lines of you

Re: Configuring Jenkins

2016-11-15 Thread Robert Bradshaw
This is great; thanks for doing this! On Tue, Nov 15, 2016 at 6:43 AM, Dan Halperin wrote: > Seems phenomenal! > > Reading between the lines of your email, it sounds like changes to Jenkins > configuration will not actually be exercised on the PR that makes them. So, > we still need to work out a

Re: Configuring Jenkins

2016-11-15 Thread Dan Halperin
Seems phenomenal! Reading between the lines of your email, it sounds like changes to Jenkins configuration will not actually be exercised on the PR that makes them. So, we still need to work out a process of how we test changes that would affect Jenkins config. (That does not take away from the f

Re: Configuring Jenkins

2016-11-15 Thread Daniel Kulp
This is very cool….. I definitely need to look at this a bit as there a few there projects that would love to have something similar. :) Dan > On Nov 15, 2016, at 4:01 AM, Davor Bonaci wrote: > > Hi everybody, > As I'm sure everybody knows, we use Apache's Jenkins instance for all our > te

Re: Configuring Jenkins

2016-11-15 Thread Thomas Weise
Very nice! On Tue, Nov 15, 2016 at 12:52 PM, Aljoscha Krettek wrote: > +1 I like this a lot! > > On Tue, 15 Nov 2016 at 10:37 Jean-Baptiste Onofré wrote: > > > Fantastic Davor ! > > > > I like this approach, I gonna take a deeper look. > > > > Thanks ! > > > > Regards > > JB > > > > On 11/15/2

Re: Configuring Jenkins

2016-11-15 Thread Aljoscha Krettek
+1 I like this a lot! On Tue, 15 Nov 2016 at 10:37 Jean-Baptiste Onofré wrote: > Fantastic Davor ! > > I like this approach, I gonna take a deeper look. > > Thanks ! > > Regards > JB > > On 11/15/2016 10:01 AM, Davor Bonaci wrote: > > Hi everybody, > > As I'm sure everybody knows, we use Apache'

Re: Configuring Jenkins

2016-11-15 Thread Jean-Baptiste Onofré
Fantastic Davor ! I like this approach, I gonna take a deeper look. Thanks ! Regards JB On 11/15/2016 10:01 AM, Davor Bonaci wrote: Hi everybody, As I'm sure everybody knows, we use Apache's Jenkins instance for all our testing, including pre-commit, post-commit, nightly snapshot, etc. (Travi

Configuring Jenkins

2016-11-15 Thread Davor Bonaci
Hi everybody, As I'm sure everybody knows, we use Apache's Jenkins instance for all our testing, including pre-commit, post-commit, nightly snapshot, etc. (Travis CI is a backup system and recommended for individual forks only.) Managing Jenkins projects has been a big pain point so far. Among oth