It is the way the pipeline plugin builds up the new Runtime to execute
Maven. If you read the JENKINS issue, you'll recognize the issue. And it
seems the Maven Project is one of the few using this pipeline plugin, no
other project has complained about failing Windows jobs.
Other (standard) Wi
This was fine before. Is it now Jenkins/Pipeline plugin issue or system
issue?
Why Linux is fine?
On Mon, Aug 13, 2018 at 6:26 PM Robert Scholte wrote:
> So that's what I've tried[1]
> It solved the 'cmd', but resulted in the next missing command: mvn
> Before going from one missing command to t
On Tue, 2018-07-24 at 21:03 +0200, Karl Heinz Marbaise wrote:
> Hi Robert,
>
> On 24/07/18 15:04, Robert Munteanu wrote:
> > Hi Karl Heinz,
> >
> > On Sat, 2018-07-21 at 00:15 +0200, Karl Heinz Marbaise wrote:
> > > Hi Robert,
> > >
> > > On 20/07/18 21:48, Robert Munteanu wrote:
> > > > Hi,
> >
So that's what I've tried[1]
It solved the 'cmd', but resulted in the next missing command: mvn
Before going from one missing command to the other I decided not to go
this way.
Robert
[1]
https://gitbox.apache.org/repos/asf?p=maven-jenkins-lib.git;a=blobdiff;f=vars/asfMavenTlpPlgnBuild.groo
This was the problem on Windows last night:
'cmd' is not recognized as an internal or external command
On Sun, Aug 12, 2018 at 12:44 PM Robert Scholte
wrote:
> Since a couple of days the builds on Windows nodes fail.
>
> Karl Heinz already created INFRA-16893[1]
> After some digging it seems t
