You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@maven.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2017/02/23 05:18:52 UTC
maven-3.x-jenkinsfile/master - build #54 - null
See https://builds.apache.org/job/maven-3.x-jenkinsfile/job/master/54/
maven-3.x-jenkinsfile/master - build #56 - null
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See https://builds.apache.org/job/maven-3.x-jenkinsfile/job/master/56/
maven-3.x-jenkinsfile/master - build #55 - null
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See https://builds.apache.org/job/maven-3.x-jenkinsfile/job/master/55/
Re: maven-3.x-jenkinsfile/master - build #54 - null
Posted by Stephen Connolly <st...@gmail.com>.
https://builds.apache.org/job/maven-3.x-jenkinsfile/job/master/56/
we are back to a blue build! w00t!
On 23 February 2017 at 12:48, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> I pushed a different work-around in https://github.com/apache/
> maven/commit/5cce371c8aee5d957d9b24e46cddc939a15aff40
>
> This also adds the *magic* resolveScm step, so if you have an integration
> test branch with the same name as your maven core branch, then the branch
> should be automatically detected and used for you... otherwise the master
> branch will be used for the integration tests
>
> On 23 February 2017 at 10:59, Christian Schulte <cs...@schulte.it> wrote:
>
>> Am 02/23/17 um 09:07 schrieb Stephen Connolly:
>> > Yes. Infra updated some Jenkins plugins and now the Windows path is too
>> > long.
>> >
>> > I need them to upgrade to branch-api 2.0.7 (released yesterday) and set
>> a
>> > system property to resolve the issue
>>
>> Good to know. I updated various build jobs of the "Maven Master Release
>> Status" view meanwhile to perform the checkout into a directory called
>> "Spaces & Special Char". Currently looking into the archetype repository
>> why this starts to fail. Others may fail due to this as well. We'll see.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
Re: maven-3.x-jenkinsfile/master - build #54 - null
Posted by Stephen Connolly <st...@gmail.com>.
I pushed a different work-around in
https://github.com/apache/maven/commit/5cce371c8aee5d957d9b24e46cddc939a15aff40
This also adds the *magic* resolveScm step, so if you have an integration
test branch with the same name as your maven core branch, then the branch
should be automatically detected and used for you... otherwise the master
branch will be used for the integration tests
On 23 February 2017 at 10:59, Christian Schulte <cs...@schulte.it> wrote:
> Am 02/23/17 um 09:07 schrieb Stephen Connolly:
> > Yes. Infra updated some Jenkins plugins and now the Windows path is too
> > long.
> >
> > I need them to upgrade to branch-api 2.0.7 (released yesterday) and set a
> > system property to resolve the issue
>
> Good to know. I updated various build jobs of the "Maven Master Release
> Status" view meanwhile to perform the checkout into a directory called
> "Spaces & Special Char". Currently looking into the archetype repository
> why this starts to fail. Others may fail due to this as well. We'll see.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: maven-3.x-jenkinsfile/master - build #54 - null
Posted by Christian Schulte <cs...@schulte.it>.
Am 02/23/17 um 09:07 schrieb Stephen Connolly:
> Yes. Infra updated some Jenkins plugins and now the Windows path is too
> long.
>
> I need them to upgrade to branch-api 2.0.7 (released yesterday) and set a
> system property to resolve the issue
Good to know. I updated various build jobs of the "Maven Master Release
Status" view meanwhile to perform the checkout into a directory called
"Spaces & Special Char". Currently looking into the archetype repository
why this starts to fail. Others may fail due to this as well. We'll see.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-3.x-jenkinsfile/master - build #54 - null
Posted by Stephen Connolly <st...@gmail.com>.
Yes. Infra updated some Jenkins plugins and now the Windows path is too
long.
I need them to upgrade to branch-api 2.0.7 (released yesterday) and set a
system property to resolve the issue
On Thu 23 Feb 2017 at 05:47, Christian Schulte <cs...@schulte.it> wrote:
> Am 02/23/17 um 06:18 schrieb Apache Jenkins Server:
> > See https://builds.apache.org/job/maven-3.x-jenkinsfile/job/master/54/
> >
>
> Turns out the "null" in the subject does not indicate a successful
> build. Maven master currently does not build successfully.
>
> Regards,
> --
> Christian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
> --
Sent from my phone
Re: maven-3.x-jenkinsfile/master - build #54 - null
Posted by Christian Schulte <cs...@schulte.it>.
Am 02/23/17 um 06:18 schrieb Apache Jenkins Server:
> See https://builds.apache.org/job/maven-3.x-jenkinsfile/job/master/54/
>
Turns out the "null" in the subject does not indicate a successful
build. Maven master currently does not build successfully.
Regards,
--
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org