Sounds good. +1. On Thu, Jun 2, 2016 at 3:28 AM Steve Loughran <ste...@hortonworks.com> wrote:
> > > On 1 Jun 2016, at 04:53, Andrew Wang <andrew.w...@cloudera.com> wrote: > > > > I'm in favor of something that helps unify the current mess of Jenkins > > jobs. We do something similar for our internal Hadoop repo: each branch > has > > a "build.sh" and "test.sh" script that builds and then runs the tests. > This > > predates Yetus, else we'd probably have used that. So +1 from me. > > +1 from me too > > > why not start with Hadoop common and if it's happy, go with the rest > > > > > > One thing I also find really helpful is riding over flaky tests, perhaps > > via: > > > > > http://maven.apache.org/surefire/maven-surefire-plugin/examples/rerun-failing-tests.html > > > > This would be great for precommit too, since right now someone has to run > > the failed tests locally to confirm they're flakes. > > > > Even better is then feeding the success/failure into a DB so you can > track > > flaky rates over time, which helps you prioritize which flaky to fix > first, > > and helps you find the change which caused the flakiness. > > > > > There's a scala project to talk to Jenkins for that; puts them into google > docs > > --------------------------------------------------------------------- > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > >
