Looks great. Thanks! On Thu, Apr 13, 2017 at 9:52 AM, Anthony Baker <aba...@pivotal.io> wrote:
> Previously we discussed splitting out the ‘flakyTest’ target into a > separate Jenkins job [1]. You can see the results here [2]. > > Here’s the job configuration: > > - Exec: `docker run --rm -v $PWD:/geode -w /geode openjdk:8 bash ./gradlew > flakyTest` > - JUnit results: **/build/test-reports-flaky/*.xml > - Run nightly, timeout after 3h > - Run on 'ubuntu && !cloud-slave’ machines > > Please let me know if you have any feedback. > > Once the flakyTest job seems to be running smoothly (ahem), I’ll update > the nightly job to run under docker and skip the flakyTest target. > > Thanks, > Anthony > > [1] http://mail-archives.apache.org/mod_mbox/geode-dev/201703. > mbox/%3cCAJrNg03PThr7UtkFS+NQXau3KN51m-CLB6M8gtZO9_ > bh0zl...@mail.gmail.com%3e <http://mail-archives.apache. > org/mod_mbox/geode-dev/201703.mbox/%3CCAJrNg03PThr7UtkFS+ > nqxau3kn51m-clb6m8gtzo9_bh0zl...@mail.gmail.com%3E> > [2] https://builds.apache.org/job/Geode-flakyTest/ < > https://builds.apache.org/job/Geode-flakyTest/> > >
