Hey Jake, On this topic. The ASF Jenkins farm has a lot of custom slave setups. Any discussion around installing a base linux and docker and testing everything in containers? Would allow all builds to run on all slaves. Right now it is sort of Ubuntu or nothing.
-Randy On Tue, Feb 16, 2016 at 6:27 AM, Jake Farrell <[email protected]> wrote: > The jira-jenkins precommit jobs run today for Hadoop and its subprojects, > they use the patch available flag in the ticket to trigger the build > > -Jake > > On Tue, Feb 16, 2016 at 5:47 AM, Jens Geyer <[email protected]> wrote: > > > Hi, > > > > > attach jira to the precommit jenkins builds also > > > > That is possible? Pulling the patch file and do a build? I was not aware > > of that. > > > > JensG > > > > ________________________________ > > Von: Jake Farrell > > Gesendet: 16.02.2016 04:37 > > An: [email protected] > > Betreff: Re: [DISCUSSION] Patches and precommits > > > > We can attach jira to the precommit jenkins builds also, but would not be > > opposed to moving to all patches landing on github as long as the > > requirement of a jira being associated with each issue is maintained > > > > -Jake > > > > On Mon, Feb 15, 2016 at 4:53 PM, Jens Geyer <[email protected]> > wrote: > > > > > Hi *, > > > > > > now that we have working precommit checks up and running (thanks for > all > > > the work, guys – that’s just great!), I wonder if we should still > accept > > > patch files, for a simple reason: Patch files added to JIRA attachments > > > obviously do not participate in the precommits. That’s unfortunate, and > > > hence does not contribute anymore to the high quality level we want. > > > > > > Is there a chance we can switch over to pull requests entirely? Or > maybe > > > we make it mandatory for changes of a certain size? But where to draw > the > > > line? Even one minorish typo at the right place can make the difference > > > between make and break. > > > > > > What do you think? > > > JensG > > >
