Re: flakyTest on Jenkins

2017-06-01 Thread Anthony Baker
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,

Re: flakyTest on Jenkins

2017-04-13 Thread Kirk Lund
Looks great. Thanks! On Thu, Apr 13, 2017 at 9:52 AM, Anthony Baker 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

flakyTest on Jenkins

2017-04-13 Thread Anthony Baker
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: