Re: broken build

2019-09-27 Thread Owen Nichols
Thanks Bruce! I’ve updated the release script to make a PR instead of committing directly to develop when adding the old version. > On Sep 27, 2019, at 5:04 PM, Bruce Schuchardt wrote: > > I've pushed changes to handle v1.10.0 in our tests > > Please don't push changes to our repo w/o running

re: broken build

2019-09-27 Thread Bruce Schuchardt
I've pushed changes to handle v1.10.0 in our tests Please don't push changes to our repo w/o running them through our tests. You might think changing something like setting.gradle isn't a big deal but in this case it exposed problems that needed to be addressed.

Re: Broken build?

2018-02-22 Thread Kirk Lund
Nevermind... On Thu, Feb 22, 2018 at 4:07 PM, Kirk Lund wrote: > My latest precheckin failed to compile with the following. This is on a > branch that I rebased on latest develop HEAD. Has this already been fixed? > > :gemfire-test:compileTestJava/tmp/build/ae3c03f4/gemfire/ > closed/gemfire-tes

Re: Broken build?

2018-02-22 Thread Patrick Rhomberg
I got a similar issue a while back. It was something weird about gradle caching, I think. If you're using `./gradlew clean installDist`, try using a pass of `./gradlew clean build` instead. That cleared it up for me. On Thu, Feb 22, 2018 at 4:07 PM, Kirk Lund wrote: > My latest precheckin fai