beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <andreas.veit...@gmail.com>
Subject Re: Jenkins build became unstable: beam_MavenVerify #14
Date Thu, 17 Mar 2016 15:08:02 GMT
It looks like nowadays, when enabling "Use private Maven repository", you
also need to select a strategy. If you want to shield the build against
pollution of the local Maven repository by other builds (which I highly
recommend, speaking from experience), you should use "Local to the
workspace". That's currently not the case for that build: it's set to
"Default (~/.m2/respository)", which doesn't sound very private...

Andreas

On Thu, Mar 17, 2016 at 2:57 PM, Amit Sela <amitsela33@gmail.com> wrote:

> Looks like the cached MapR Hadoop dependencies issue is back..
> I didn't push anything lately, and the only commit was unrelated.
>
> On Thu, Mar 17, 2016 at 4:54 PM Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>
> > See <https://builds.apache.org/job/beam_MavenVerify/14/changes>
> >
> >
>

Mime
View raw message