Artifacts of jenkins build

[Dan Smith <ds...@pivotal.io>]

Would it be possible to archive the **/*-progress.txt files as part of the
jenkins build? I was recently trying to track down the why a test failed,
and it looked like it was due to a previous test. If we had those files I
could figure out what the previous tests were. Who has authority to
configure this?

https://builds.apache.org/job/Geode-nightly/

Re: Artifacts of jenkins build

[Dan Smith <ds...@pivotal.io>]

Ok, thanks! I'm working on what might a better solution anyway - record the
previously run tests in the log of each test. That might be easier for
people to see and limit the scope of what previously run tests they need to
worry about.

-Dan

On Wed, Sep 9, 2015 at 6:15 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:

> Mark has Jenkins karma. If he doesn't get to it soon ping me tomorrow.
>
> On Wed, Sep 2, 2015 at 5:31 PM, Dan Smith <ds...@pivotal.io> wrote:
> > Would it be possible to archive the **/*-progress.txt files as part of
> the
> > jenkins build? I was recently trying to track down the why a test failed,
> > and it looked like it was due to a previous test. If we had those files I
> > could figure out what the previous tests were. Who has authority to
> > configure this?
> >
> > https://builds.apache.org/job/Geode-nightly/
>

Re: Artifacts of jenkins build

[Roman Shaposhnik <ro...@shaposhnik.org>]

Mark has Jenkins karma. If he doesn't get to it soon ping me tomorrow.

On Wed, Sep 2, 2015 at 5:31 PM, Dan Smith <ds...@pivotal.io> wrote:
> Would it be possible to archive the **/*-progress.txt files as part of the
> jenkins build? I was recently trying to track down the why a test failed,
> and it looked like it was due to a previous test. If we had those files I
> could figure out what the previous tests were. Who has authority to
> configure this?
>
> https://builds.apache.org/job/Geode-nightly/