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.groovy;h=5ac5f46a2f67fb6d2352b16558a514c1178b00a9;hp=04ad8533955bbafda77a94b7c79df9f466e8f337;hb=1d2d71ddef8f53c4d9e1a306215ff1b137677adc;hpb=0f9199b3f10021cdbf9b0df3d1e782048542901e
On Mon, 13 Aug 2018 08:59:12 +0200, Stephen Connolly
<[email protected]> wrote:
If we wrap our calls to bat in a withEnv step that adds the required bit
to
PATH that seems like it would resolve the issue... but probably more
pragmatic to just roll back the plugin for now...
On Sun 12 Aug 2018 at 11:44, Robert Scholte <[email protected]> wrote:
Since a couple of days the builds on Windows nodes fail.
Karl Heinz already created INFRA-16893[1]
After some digging it seems that JENKINS-44334[2] is the root cause.
It seems there's no solution yet, so maybe going back to the previous
Pipeline:Job plugin is the best option right now.
If some have other ideas, please respond to INFRA-16893[1]
thanks,
Robert
[1] https://issues.apache.org/jira/browse/INFRA-16893
[2] https://issues.jenkins-ci.org/browse/JENKINS-44334
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Sent from my phone
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
