Re: Jenkins build became unstable: beam_MavenVerify #14

[Davor Bonaci]

Adding Jason explicitly. This is somewhat expected.

Thanks Andreas.

On Thu, Mar 17, 2016 at 8:08 AM, Andreas Veithen 
wrote:

> 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  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 <
>> jenk...@builds.apache.org> wrote:
>>
>> > See 
>> >
>> >
>>
>
>

Re: Jenkins build became unstable: beam_MavenVerify #14

[Amit Sela]

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 <
jenk...@builds.apache.org> wrote:

> See 
>
>

Re: Jenkins build became unstable: beam_MavenVerify #14

[Andreas Veithen]

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  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 <
> jenk...@builds.apache.org> wrote:
>
> > See 
> >
> >
>

Re: Jenkins build became unstable: beam_MavenVerify #14

[Jason Kuster]

We've applied the change (local to the workspace) to both Jenkins projects
- hopefully this will fix. We'll keep an eye out for breakages related to
this.

On Thu, Mar 17, 2016 at 10:29 AM, Davor Bonaci  wrote:

> Adding Jason explicitly. This is somewhat expected.
>
> Thanks Andreas.
>
> On Thu, Mar 17, 2016 at 8:08 AM, Andreas Veithen <
> andreas.veit...@gmail.com> wrote:
>
>> 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  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 <
>>> jenk...@builds.apache.org> wrote:
>>>
>>> > See 
>>> >
>>> >
>>>
>>
>>
>


-- 
---
Jason Kuster
SETI - Cloud Dataflow