So I finally got some time to look into this again! I split the flakyTest target [3] [4] out of the Geode-nightly [1] and Geode-release [2] jobs. The *-flaky jobs will always run after the parent job even if it was not successful.
If you see something amiss, please let me know. Thanks, Anthony [1] https://builds.apache.org/job/Geode-nightly/ [2] https://builds.apache.org/job/Geode-nightly-flaky/ [3] https://builds.apache.org/job/Geode-release/ [4] https://builds.apache.org/job/Geode-release-flaky/ > On Apr 13, 2017, at 12:00 PM, Kirk Lund <kl...@apache.org> wrote: > > Looks great. Thanks! > > On Thu, Apr 13, 2017 at 9:52 AM, Anthony Baker <aba...@pivotal.io > <mailto: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 <mailto:bh0zl...@mail.gmail.com>%3e >> <http://mail-archives.apache <http://mail-archives.apache/>. >> org/mod_mbox/geode-dev/201703.mbox/%3CCAJrNg03PThr7UtkFS+ >> nqxau3kn51m-clb6m8gtzo9_bh0zl...@mail.gmail.com >> <mailto:nqxau3kn51m-clb6m8gtzo9_bh0zl...@mail.gmail.com>%3E> >> [2] https://builds.apache.org/job/Geode-flakyTest/ >> <https://builds.apache.org/job/Geode-flakyTest/> < >> https://builds.apache.org/job/Geode-flakyTest/ >> <https://builds.apache.org/job/Geode-flakyTest/>>
