Re: maven-3.x-jenkinsfile/master - build #54 - null

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.conno...@gmail.com> wrote: > I pushed a different work-around in https://github.com/apache/ >

Re: maven-3.x-jenkinsfile/master - build #54 - null

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

Re: maven-3.x-jenkinsfile/master - build #54 - null

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

Re: maven-3.x-jenkinsfile/master - build #54 - null

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 wrote: > Am 02/23/17 um 06:18 schrieb

Re: maven-3.x-jenkinsfile/master - build #54 - null

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