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 <[email protected]> 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: [email protected] > For additional commands, e-mail: [email protected] > >
