I have enabled the Yetus based build system based on feedback and after correcting some minor issues (enabling findbugs)
https://builds.apache.org/job/PreCommit-TEZ-Build I have archived the previous build, so manual builds can be submitted in the case of issues with the Yetus based system. https://builds.apache.org/job/PreCommit-TEZ-Build-NoYetus Please submit feedback and issues and I'll try to correct them quickly jeagles On Mon, Oct 1, 2018 at 8:33 AM, Kuhu Shukla <[email protected]> wrote: > Thank you Jon for the prototype. I am in support of moving to Yetus. Branch > targeting, GitHub PR requests and additional features like whitespace and > check-style warnings would be very useful. > > Regards, > Kuhu > > On Fri, Sep 28, 2018 at 4:23 PM Jaume Marhuenda < > [email protected]> > wrote: > > > Thank you for taking a look into this. I think this is a great idea. > > Personally, I’ve missed being able to target a particular branch to run > the > > tests against when submitting a patch in JIRA and getting the tests to > run > > just by opening a PR in github. > > > > Best, > > Jaume > > > > On 9/28/18, 12:03 PM, "Jonathan Eagles" <[email protected]> wrote: > > > > Devs, > > > > I have prototyped a Yetus based build system for Tez. The system has > a > > number of features that would enabled better supporting builds and > > further > > the ease for development. Specifically, Yetus has support for patches > > targeting, increased static analysis, support for docker builds > > (currently > > disabled for tez), targeted tests run, and support for github PR > > requests > > (currently untested). > > > > I have submitted some tests patches in > > https://issues.apache.org/jira/browse/TEZ-3891 to for devs to > > evaluate the > > features. > > > > Do devs want to migrate this system? And if so what features need to > be > > supported before migrating to this system permanently? > > > > Regards, > > jeagles > > > > > > >
