Ah, could be - anyone else can shed some light on whether using 'sh' in
expression {} in declarative pipeline is fully supported or just happens to
work sometimes?
pipeline {
[...]
stages {
stage('Maven build') {
when {
expression {
> On 15. Jan 2018, at 23:05, ST wrote:
>
> Any input appreciated!
>
Not sure but maybe pipeline steps like 'sh' aren't supposed to be used in when
expression blocks?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this
Some additional info:
The Jenkins log file reports the same StackOverflowException, and in
addition also reports this exception:
Jan 15, 2018 11:07:46 PM org.jenkinsci.plugins.workflow.job.WorkflowRun
finish
INFO: MY_MULTIBRANCH-PIPELINE/master #253 completed: FAILURE
Jan 15, 2018 11:07:46 PM
org.
I am seeing a StackOverflowException in
org.jboss.marshalling.river.RiverMarshaller in a declarative Jenkins
pipeline. The
interesting thing is that it occurs *only* just after having restarted
the Jenkins instance. After building it once or twice,
the next build usually works fine. Also when waiti
