Re: fix geode-old-versions downloads with a clean build?

[Dan Smith]

I submitted a PR to try to cache the old version somewhere else but people
didn't like the approach I took so I closed it. If someone wants to take
this up that would be great, I'm don't really have time to mess with it
right now.

https://github.com/apache/geode/pull/733

-Dan

On Wed, Sep 6, 2017 at 9:47 AM, Mark Hanson  wrote:

> There was discussion about taking that out I am very hopeful that it
> happens.
>
> Thanks,
> Mark
>
> On Wed, Sep 6, 2017 at 9:25 AM, Galen O'Sullivan 
> wrote:
>
> > Hi all,
> >
> > I like to run a `./gradlew clean build` when I'm pulling, reviewing, or
> > about to push a new build. It seems that this causes the cached geode zip
> > files to have to be redownloaded, which means that the build takes 10
> > minutes instead of 2. If I'm touching a couple of branches a day, this
> can
> > result in significant wasted time. Is there a way to run a clean build
> > without resetting these tests?
> >
> > Thanks,
> > Galen
> >
>

Re: fix geode-old-versions downloads with a clean build?

[Mark Hanson]

There was discussion about taking that out I am very hopeful that it
happens.

Thanks,
Mark

On Wed, Sep 6, 2017 at 9:25 AM, Galen O'Sullivan 
wrote:

> Hi all,
>
> I like to run a `./gradlew clean build` when I'm pulling, reviewing, or
> about to push a new build. It seems that this causes the cached geode zip
> files to have to be redownloaded, which means that the build takes 10
> minutes instead of 2. If I'm touching a couple of branches a day, this can
> result in significant wasted time. Is there a way to run a clean build
> without resetting these tests?
>
> Thanks,
> Galen
>

fix geode-old-versions downloads with a clean build?

[Galen O'Sullivan]

Hi all,

I like to run a `./gradlew clean build` when I'm pulling, reviewing, or
about to push a new build. It seems that this causes the cached geode zip
files to have to be redownloaded, which means that the build takes 10
minutes instead of 2. If I'm touching a couple of branches a day, this can
result in significant wasted time. Is there a way to run a clean build
without resetting these tests?

Thanks,
Galen