You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by Amit Sela <am...@gmail.com> on 2016/03/17 15:57:52 UTC
Re: Jenkins build became unstable: beam_MavenVerify #14
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>
>
>
Re: Jenkins build became unstable: beam_MavenVerify #14
Posted by Jason Kuster <ja...@google.com.INVALID>.
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 <da...@google.com> wrote:
> Adding Jason explicitly. This is somewhat expected.
>
> Thanks Andreas.
>
> On Thu, Mar 17, 2016 at 8:08 AM, Andreas Veithen <
> andreas.veithen@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 <am...@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>
>>> >
>>> >
>>>
>>
>>
>
--
-------
Jason Kuster
SETI - Cloud Dataflow
Re: Jenkins build became unstable: beam_MavenVerify #14
Posted by Davor Bonaci <da...@google.com>.
Adding Jason explicitly. This is somewhat expected.
Thanks Andreas.
On Thu, Mar 17, 2016 at 8:08 AM, Andreas Veithen <an...@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 <am...@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>
>> >
>> >
>>
>
>
Re: Jenkins build became unstable: beam_MavenVerify #14
Posted by Davor Bonaci <da...@google.com.INVALID>.
Adding Jason explicitly. This is somewhat expected.
Thanks Andreas.
On Thu, Mar 17, 2016 at 8:08 AM, Andreas Veithen <an...@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 <am...@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>
>> >
>> >
>>
>
>
Re: Jenkins build became unstable: beam_MavenVerify #14
Posted by Andreas Veithen <an...@gmail.com>.
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 <am...@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>
> >
> >
>
Re: Jenkins build became unstable: beam_MavenVerify #14
Posted by Andreas Veithen <an...@gmail.com>.
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 <am...@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>
> >
> >
>