Well, adding a new JDK in Jenkins Tools pointing to the Windows path of
Java worked
Then withMaven(jdk: "jdk1.8-win")
I have though hit another snag. Lots of ERROR after build success.
ERROR: [withMaven] WARNING: Exception archiving and fingerprinting
MavenArtifact{no.spacetec:myApp:jar:1.0.0-SN
I took a look at the Maven Pipeline documentation again.
For Windows it says to use bat, not sh. I tried that, and got a little bit
closer, but now it cannot find JAVA_HOME
- withMaven Wrapper script -
Error: JAVA_HOME is set to an invalid directory.
JAVA_HOME = "/usr/java/jdk1.8.0_102"
I have connected a Windows slave to Jenkins with SSH+Cygwin.
So running shell scripts like "sh 'mvn'" should work as I do it locally on
the Windows.
Running withMaven fails, and I cannot figure our why.
[Pipeline] node
Running on master-windows-x86_64 in
/home/username/workspace/myApp_username_
+1, awesome idea. An entry like the "State of Jenkins Pipeline Testing" on
jenkins.io would certainly be much useful to help this subject mature. And
to that end we probably need more people trying different strategies to see
what works well or less well. Hence trying to list the current strategies
Hello,
How can I distinguish between a job that was aborted by timeout and a job
that was aborted by a user (clicking the red X button)?
*try {*
* *
* } catch (hudson.AbortException e) {*
*//catching an exception if job was aborted - both by
user/timeout*
*} catch
