[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container

48 views
Skip to first unread message

srinidhesivakumar@gmail.com (JIRA)

unread,
Nov 4, 2019, 9:18:02 AM11/4/19
to jenkinsc...@googlegroups.com
srinidhi Sivakumar created an issue
 
Jenkins / Bug JENKINS-60039
durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Issue Type: Bug Bug
Assignee: Carlos Sanchez
Components: docker, docker-plugin, durable-task-plugin, pipeline
Created: 2019-11-04 14:17
Environment: Ubuntu 18.04
Jenkins v. 2.190.1 (installed by apt-get, not in container)
Durable Task Plugin v. 1.33
Priority: Blocker Blocker
Reporter: srinidhi Sivakumar

Tested on Durable Task Plugin v. 1.29 & v. 1.30 wasn't worked.

    • Durable Task Plugin has been "updated to v. 1.33". Still the problem isn't resolved.**

 

PIPELINE:

pipeline {
    agent {
         docker

{                label 'buildserver'                image 'busybox'                args '-v /var/lib/jenkins/caches:/jenkins/caches'                args '-v /var/lib/jenkins/workspace:/jenkins/workspace'                args '-u root'                      }

             }
   stages {
      stage("Test sh script in container") {
         steps

{              sh label: 'Echo "Hello World...', script: 'echo "Hello World!"'                           }

                  }
            }
    }

 

ERROR:
[Pipeline] Start of Pipeline[Pipeline] nodeRunning on buildserver in c:/jenkins/workspace/<project-name>[Pipeline] {[Pipeline] stage[Pipeline]

{ (Declarative: Checkout SCM)[Pipeline] checkout[Pipeline] }

[Pipeline] // stage[Pipeline] withEnv[Pipeline]

{[Pipeline] isUnix[Pipeline] sh*process apparently never started in c:/jenkins/workspace/<project-name>@tmp/durable-73ba6e89 (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)* [Pipeline] }

[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code -2
Finished: FAILURE
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

srinidhesivakumar@gmail.com (JIRA)

unread,
Nov 4, 2019, 9:20:02 AM11/4/19
to jenkinsc...@googlegroups.com
srinidhi Sivakumar updated an issue
Change By: srinidhi Sivakumar
* Tested on Durable Task Plugin v. 1.29 & v. 1.30 wasn't worked. *

** * Durable Task Plugin has been *   * "updated to v. 1.33". Still the problem isn't resolved. ***

 

 * PIPELINE: *

pipeline {
    agent {
         docker {                

               label 'buildserver'                

               image 'busybox'                

               args '-v /var/lib/jenkins/caches:/jenkins/caches'                

               args '-v /var/lib/jenkins/workspace:/jenkins/workspace'
               

              args '-u root'                      

                          }
             }
   stages {
      stage("Test sh script in container") {
         steps {              

             sh label: 'Echo "Hello World...', script: 'echo "Hello World!"'
           

                        }
                  }
            }
    }

 

*ERROR:*
[Pipeline] Start of Pipeline[Pipeline] nodeRunning on [buildserver|http://192.168.8.247:8081/computer/contusbuildserver/] in c:/jenkins/workspace/<project-name>[Pipeline] {[Pipeline] stage[Pipeline]

{ (Declarative: Checkout SCM)[Pipeline] checkout[Pipeline] }

[Pipeline] // stage[Pipeline] withEnv[Pipeline]

{[Pipeline] isUnix[Pipeline] sh*process apparently never started in c:/jenkins/workspace/<project-name>@tmp/durable-73ba6e89
(running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)*
[Pipeline] }

[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code -2
Finished: FAILURE

srinidhesivakumar@gmail.com (JIRA)

unread,
Nov 4, 2019, 9:24:03 AM11/4/19
to jenkinsc...@googlegroups.com
srinidhi Sivakumar updated an issue
Tested on Durable Task Plugin v. 1.29 & v. 1.30 wasn't worked.

Durable Task Plugin has been "updated to v. 1.33". Still the problem isn't resolved.

 

*PIPELINE:*

pipeline {
    agent {
         docker {

               

               label 'buildserver'

               

               image 'busybox'

               

               args '-v /var/lib/jenkins/caches:/jenkins/caches'

               

               args '-v /var/lib/jenkins/workspace:/jenkins/workspace'

               

              args '-u root'                      

                          }

             
}
   stages {
      stage ("Test sh script in container") {
         steps {

             

             sh label: 'Echo "Hello World...', script: 'echo "Hello World!"'            

                            }

                  }
            }
    }

 

*ERROR:*
[Pipeline] Start of Pipeline

[Pipeline] nodeRunning on [buildserver|http://192.168.8.247:8081/computer/contusbuildserver/] in c:/jenkins/workspace/<project-name>

[Pipeline] {

[Pipeline] stage

[Pipeline]

{ (Declarative: Checkout SCM)

[Pipeline] checkout

[Pipeline] }

[Pipeline] // stage

[Pipeline] withEnv

[Pipeline] {

{ [Pipeline] isUnix[Pipeline] sh * process apparently never started in c:/jenkins/workspace/<project-name>@tmp/durable-73ba6e89 (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer) *

[Pipeline] }

[Pipeline] // withEnv

[Pipeline] }

[Pipeline] // node

[Pipeline] End of PipelineERROR Pipeline

ERROR : script returned exit code -2
Finished: FAILURE

srinidhesivakumar@gmail.com (JIRA)

unread,
Nov 4, 2019, 9:26:03 AM11/4/19
to jenkinsc...@googlegroups.com
{ [Pipeline] isUnix[Pipeline] sh process apparently never started in c:/jenkins/workspace/<project-name>@tmp/durable-73ba6e89 (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)

[Pipeline] }

[Pipeline] // withEnv

[Pipeline] }

[Pipeline] // node

[Pipeline] End of Pipeline


ERROR: script returned exit code -2
Finished: FAILURE

srinidhesivakumar@gmail.com (JIRA)

unread,
Nov 4, 2019, 9:28:03 AM11/4/19
to jenkinsc...@googlegroups.com

alex.katz@caspar.ai (JIRA)

unread,
Nov 4, 2019, 5:42:03 PM11/4/19
to jenkinsc...@googlegroups.com
Alex Katz commented on Bug JENKINS-60039
 
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container

I'm encountering the same issue on Amazon Linux 2018.03 and Ubuntu 18.04

alex.katz@caspar.ai (JIRA)

unread,
Nov 4, 2019, 5:43:02 PM11/4/19
to jenkinsc...@googlegroups.com
Alex Katz edited a comment on Bug JENKINS-60039
I'm encountering the same a similar issue on Amazon Linux 2018.03 and Ubuntu 18.04 with the same error message.

alex.katz@caspar.ai (JIRA)

unread,
Nov 4, 2019, 5:57:03 PM11/4/19
to jenkinsc...@googlegroups.com
Alex Katz edited a comment on Bug JENKINS-60039
I'm encountering the a similar same issue on Amazon Linux 2018.03 and Ubuntu 18.04 with the same error message.

alex.katz@caspar.ai (JIRA)

unread,
Nov 4, 2019, 6:03:02 PM11/4/19
to jenkinsc...@googlegroups.com
Alex Katz edited a comment on Bug JENKINS-60039
I'm encountering the same issue error message on Ubuntu 18.04 except it seems to be breaking a git checkout step and possibly other sh steps.

alex.katz@caspar.ai (JIRA)

unread,
Nov 4, 2019, 6:04:01 PM11/4/19
to jenkinsc...@googlegroups.com
Alex Katz edited a comment on Bug JENKINS-60039
I'm encountering the same error message on Ubuntu 18.04 except it seems to be breaking a git checkout step and possibly other sh steps , not in a docker container .

alex.katz@caspar.ai (JIRA)

unread,
Nov 4, 2019, 6:07:03 PM11/4/19
to jenkinsc...@googlegroups.com
Alex Katz edited a comment on Bug JENKINS-60039
I'm encountering the same error message on Ubuntu 18.04 except it seems to be breaking a git checkout step and possibly other sh steps, not in a docker container. Also running durable-task v1.33 but also running lots of other plugins and I haven't tried reproducing the issue on clean system yet.

alex.katz@caspar.ai (JIRA)

unread,
Nov 4, 2019, 6:28:02 PM11/4/19
to jenkinsc...@googlegroups.com
Alex Katz edited a comment on Bug JENKINS-60039
I'm encountering the same error message on Ubuntu 18.04 except it seems to be breaking a git checkout step ({{checkout scm}}) and possibly other sh steps, not in a docker container. Also running durable-task v1.33 but also running lots of other plugins and I haven't tried reproducing the issue on clean system yet.

cchiou@cloudbees.com (JIRA)

unread,
Nov 6, 2019, 5:51:05 PM11/6/19
to jenkinsc...@googlegroups.com

Just noting that the title is a bit misleading. If I read this right, it looks like you have a failed shell step and that it has not been working on 1.29, 1.30, and 1.33. It's not that the upgrade to 1.33 has broken your pipeline correct?

Is there any way you can run your pipeline again with org.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true and posting the output here? That might give a better idea of what's going on.

alex.katz@caspar.ai (JIRA)

unread,
Nov 6, 2019, 6:03:02 PM11/6/19
to jenkinsc...@googlegroups.com
Alex Katz edited a comment on Bug JENKINS-60039
I'm encountering the same error message on Ubuntu 18.04 except it seems to be breaking a git checkout step ({{checkout scm}}) and possibly other sh steps, not in a docker container. Also running durable-task v1.33 but also running lots of other plugins and I haven't tried reproducing the issue on clean system yet.


Update: Rebuilt Jenkins (with the same plugins and configuration) and now all of the pipelines work as expected, not sure what was causing it to break before.

timblaktu@gmail.com (JIRA)

unread,
Mar 5, 2020, 10:31:04 AM3/5/20
to jenkinsc...@googlegroups.com

We're having same problem, but it's not yet clear what change caused the behavior. We are on durable task plugin v1.33, however we have not updated this recently to my knowledge (and I haven't been able to find plugin update history anywhere - any advice?) 

The signature of the build failures is that the `withDockerContainer` step completes successfully, and the pipeline begins to run the sh command (the first step in the `withDockerContainer` clause) and there's no apparent activity (other than the seemingly normal output in the durable task plugin loggers) for 5 minutes, then the failure message as the OP here. Here is what the durable task loggers output during those 5 minutes:

```
Mar 05, 2020 7:03:57 AM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep  seems to be online so using /var/lib/jenkins/workspace/TesiraFirmwareNG_develop Mar 05, 2020 7:03:57 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep still running in /var/lib/jenkins/workspace/TesiraFirmwareNG_develop on
```
After 5 minutes, I then see:

```
Mar 05, 2020 7:05:12 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
calling close with nl=true
Mar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[101:sh]:OwnerTesiraFirmwareNG/develop/42:TesiraFirmwareNG/develop #42
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
launching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@722b273b
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript
launching [nohup, sh, c, ({ while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859' -a ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt'; sleep 3; done } & jsc=durable-97017349f4d4de030acf9aecc2fb49fa; JENKINS_SERVER_COOKIE=$$jsc 'sh' -xe '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/script.sh' > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt' 2>&1; echo $$? > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt'; wait) >& 2>&- &]
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
launched task
Mar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[102:sh]:OwnerTesiraFirmwareNG/develop/42:TesiraFirmwareNG/develop #42
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
launching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@460edded
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript
launching [nohup, sh, c, ({ while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0' -a ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-log.txt'; sleep 3; done } & jsc=durable-97017349f4d4de030acf9aecc2fb49fa; JENKINS_SERVER_COOKIE=$$jsc 'sh' -xe '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/script.sh' > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-log.txt' 2>&1; echo $$? > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-result.txt'; wait) >& 2>&- &]
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
launched task
Mar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[103:sh]:OwnerTesiraFirmwareNG/develop/42:TesiraFirmwareNG/develop #42
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
launching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@6864647
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript
launching [nohup, sh, c, ({ while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f' -a ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-log.txt'; sleep 3; done } & jsc=durable-97017349f4d4de030acf9aecc2fb49fa; JENKINS_SERVER_COOKIE=$$jsc 'sh' -xe '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/script.sh' > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-log.txt' 2>&1; echo $$? > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-result.txt'; wait) >& 2>&- &]
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
launched task
Mar 05, 2020 7:05:14 AM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
seems to be online so using /var/lib/jenkins/workspace/TesiraFirmwareNG_develop
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
creating filtered stream
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.FileMonitoringTask
remote transcoding charset: null
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.FileMonitoringTask
copied 686 bytes from /var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript
found exit code 0 in /var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
calling close with nl=true
Mar 05, 2020 7:05:14 AM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
seems to be online so using /var/lib/jenkins/workspace/TesiraFirmwareNG_develop
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
creating filtered stream
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.FileMonitoringTask
remote transcoding charset: null
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.FileMonitoringTask
copied 334 bytes from /var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-log.txt
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript
found exit code 0 in /var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
calling close with nl=true
Mar 05, 2020 7:05:14 AM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
seems to be online so using /var/lib/jenkins/workspace/TesiraFirmwareNG_develop
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
creating filtered stream
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.FileMonitoringTask
remote transcoding charset: null
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.FileMonitoringTask
copied 189 bytes from /var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-log.txt
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript
found exit code 0 in /var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
calling close with nl=true

```

Nothing looks suspicious to me here, but I'm unfamiliar with this plugin before last night. Let me know if you can glean anything from this.

I will look into running with the LAUNCH_DIAGNOSTICS suggestion, but in the meantime, since the changelogs singe 1.29 for this plugin indicate instability, I'm inclined to revert and test.

Let me know if you hav eother suggestions.
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

timblaktu@gmail.com (JIRA)

unread,
Mar 5, 2020, 10:36:04 AM3/5/20
to jenkinsc...@googlegroups.com
Tim Black edited a comment on Bug JENKINS-60039
We're having same problem, but it's not yet clear what change caused the behavior. We are on durable task plugin v1.33, and [Jenkins ver. 2.190.3|https://jenkins.io/], however we have not updated this recently to my knowledge (and I haven't been able to find plugin update history anywhere - any advice?)   .

The signature of the build failures is that the `withDockerContainer` step completes successfully, and the pipeline begins to run the sh command (the first step in the `withDockerContainer` clause) and there's no apparent activity (other than the seemingly normal output in the durable task plugin loggers) for 5 minutes, then the failure message as the OP here. Here is what the durable task loggers output during those 5 minutes:

```  
{code:java}
 Mar 05, 2020 7:03:57 AM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep  seems to be online so using /var/lib/jenkins/workspace/TesiraFirmwareNG_develop Mar 05, 2020 7:03:57 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep still running in /var/lib/jenkins/workspace/TesiraFirmwareNG_develop on {code}
```
After 5 minutes, I then see:

```  

 
{code:java}
Mar 05, 2020 7:05:12 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
calling close with nl=true
Mar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[101:sh]: Owner[TesiraFirmwareNG OwnerTesiraFirmwareNG /develop/42:TesiraFirmwareNG/develop #42 ]
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
launching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@722b273b
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript
launching [nohup, sh, - c, ( \ { while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859' -a \ ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt'; sleep 3; done } & jsc=durable-97017349f4d4de030acf9aecc2fb49fa; JENKINS_SERVER_COOKIE=$$jsc 'sh' -xe '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/script.sh' > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt' 2>&1; echo $$? > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt'; wait) >& - 2>&- &]

Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
launched task
Mar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[102:sh]: Owner[TesiraFirmwareNG OwnerTesiraFirmwareNG /develop/42:TesiraFirmwareNG/develop #42 ]
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
launching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@460edded
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript
launching [nohup, sh, - c, ( \ { while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0' -a \ ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-log.txt'; sleep 3; done } & jsc=durable-97017349f4d4de030acf9aecc2fb49fa; JENKINS_SERVER_COOKIE=$$jsc 'sh' -xe '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/script.sh' > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-log.txt' 2>&1; echo $$? > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-result.txt'; wait) >& - 2>&- &]

Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
launched task
Mar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[103:sh]: Owner[TesiraFirmwareNG OwnerTesiraFirmwareNG /develop/42:TesiraFirmwareNG/develop #42 ]
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep
launching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@6864647
Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript
launching [nohup, sh, - c, ( \ { while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f' -a \ ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-log.txt'; sleep 3; done } & jsc=durable-97017349f4d4de030acf9aecc2fb49fa; JENKINS_SERVER_COOKIE=$$jsc 'sh' -xe '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/script.sh' > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-log.txt' 2>&1; echo $$? > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a9f0797f/jenkins-result.txt'; wait) >& - 2>&- &]
{code}
```
Nothing looks suspicious to me here, but I'm unfamiliar with this plugin before last night. Let me know if you can glean anything from this.

I will look into running with the LAUNCH_DIAGNOSTICS suggestion, but in the meantime, since the changelogs singe 1.29 for this plugin indicate instability, I'm inclined to revert and test.

Let me know if you hav eother have other suggestions.

timblaktu@gmail.com (JIRA)

unread,
Mar 5, 2020, 10:52:03 AM3/5/20
to jenkinsc...@googlegroups.com

REverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer { sh }, results in this:

Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] Start of Pipeline
[Pipeline] End of Pipeline
java.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps [ansiblePlaybook, ansibleVault, build, checkout, emailext, emailextrecipients, findFiles, git, input, jiraComment, jiraIssueSelector, jiraSearch, junit, library, libraryResource, load, lock, milestone, nodesByLabel, office365ConnectorSend, parallel, properties, publishHTML, readCSV, readJSON, readManifest, readMavenPom, readProperties, readTrusted, readYaml, resolveScm, sha1, slackSend, slackUploadFile, stage, svn, tee, timestamps, tm, touch, unzip, withCredentials, writeCSV, writeJSON, writeMavenPom, writeYaml, xunit, zip] or symbols [AUnit, BoostTest, CTest, CUnit, Check, CppTest, CppUnit, Custom, FPCUnit, GoogleTest, JUnit, MSTest, MbUnit, NUnit2, NUnit3, PHPUnit, QtTest, UnitTest, Valgrind, all, always, ant, antFromApache, antOutcome, antTarget, apiToken, architecture, archiveArtifacts, artifactManager, authorizationMatrix, batchFile, bitbucket, booleanParam, brokenBuildSuspects, brokenTestsSuspects, buildAllBranches, buildAnyBranches, buildButton, buildChangeRequests, buildDiscarder, buildNamedBranches, buildNoneBranches, buildParameter, buildRegularBranches, buildSelector, buildTags, caseInsensitive, caseSensitive, certificate, choice, choiceParam, clock, cloud, command, configFile, configFileProvider, copyArtifactPermission, copyArtifacts, credentials, cron, crumb, culprits, defaultView, demand, developers, disableConcurrentBuilds, disableResume, dockerCert, downloadSettings, downstream, dumb, durabilityHint, embUnit, envInject, envVars, exact, extendedChoice, failed, file, fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, git, gitBranchDiscovery, gitHubBranchDiscovery, gitHubBranchHeadAuthority, gitHubForkDiscovery, gitHubSshCheckout, gitHubTagDiscovery, gitHubTrustContributors, gitHubTrustEveryone, gitHubTrustNobody, gitHubTrustPermissions, gitParameter, gitTagDiscovery, github, githubPush, globalConfigFiles, gtester, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, inheriting, inheritingGlobal, installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobName, lastCompleted, lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, lastSuccessful, lastWithArtifacts, latestSavedBuild, legacy, legacySCM, list, local, location, logRotator, loggedInUsersCanDoAnything, masterBuild, maven, maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, modernSCM, myView, nodeProperties, nonInheriting, none, office365ConnectorSend, office365ConnectorWebhooks, overrideIndexTriggers, paneStatus, parameters, passed, password, pattern, permalink, permanent, pipelineTriggers, plainText, plugin, pollSCM, projectNamingStrategy, proxy, queueItemAuthenticator, quietPeriod, rateLimitBuilds, recipients, regex, requestor, run, runParam, sSHLauncher, schedule, scmRetryCount, scriptApproval, scriptApprovalLink, search, security, shell, skipped, slackNotifier, slave, sourceRegexFilter, sourceWildcardFilter, specific, ssh, sshUserPrivateKey, stackTrace, standard, status, string, stringParam, swapSpace, text, textParam, tmpSpace, toolLocation, unsecured, upstream, upstreamDevelopers, userSeed, usernameColonPassword, usernamePassword, viewsTabBar, weather, wildcards, withAnt, workspace, xUnitDotNet, zfs, zip] or globals [currentBuild, env, params, scm]
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:202)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:160)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:157)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:142)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:158)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:162)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
at WorkflowScript.run(WorkflowScript:1)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46)
at com.cloudbees.groovy.cps.Next.step(Next.java:83)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)
at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:185)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:370)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:93)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:282)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:270)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE

 

timblaktu@gmail.com (JIRA)

unread,
Mar 5, 2020, 10:56:04 AM3/5/20
to jenkinsc...@googlegroups.com
Tim Black edited a comment on Bug JENKINS-60039
REverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in the below error. Note that we are using PERFORMANCE_OPTIMIZED durability level for this : job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. __ 
{code:java}
{code}
 

timblaktu@gmail.com (JIRA)

unread,
Mar 5, 2020, 11:24:09 AM3/5/20
to jenkinsc...@googlegroups.com
Tim Black edited a comment on Bug JENKINS-60039
REverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in the below error (UPDATE:
I see on our "manage plugin" page that this error is due to an unmet dependency:Pipeline: Nodes and Processes version 2 . 35Durable Task Plugin version 1.29 is older than required. To fix, install version 1.33 or later.)
. Note that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. __ 

timblaktu@gmail.com (JIRA)

unread,
Mar 5, 2020, 11:31:03 AM3/5/20
to jenkinsc...@googlegroups.com
Tim Black edited a comment on Bug JENKINS-60039
REverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in the below error ( .

 UPDATE:
I see on our "manage plugin" page that this error is due to an unmet dependency: " Pipeline: Nodes and Processes version 2. 35Durable 35" "Durable  Task Plugin version 1.29 is older than required. To fix, install version 1.33 or later. ) "

timblaktu@gmail.com (JIRA)

unread,
Mar 5, 2020, 11:42:05 AM3/5/20
to jenkinsc...@googlegroups.com
Tim Black edited a comment on Bug JENKINS-60039
REverting Reverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in the below an error .

UPDATE: I see on our "manage plugin" page that this error is due to an unmet dependency : " between Durable Task and Pipeline: Nodes and Processes  version 2 . 35" "Durable Task Plugin version 1 So I went back to DT v1 . 29 is older than required. To fix, install version 1. 33  or later since I'm not immediately sure how to resolve this dependency heck . "

Note In the meantime, I have noticed that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots.  __ 

timblaktu@gmail.com (JIRA)

unread,
Mar 5, 2020, 11:44:02 AM3/5/20
to jenkinsc...@googlegroups.com
Tim Black edited a comment on Bug JENKINS-60039
Reverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in an error due to an unmet dependency between Durable Task and Pipeline: Nodes and Processes. So I went back to DT v1.33 since I'm not immediately sure how to resolve this dependency heck.


In the meantime, I have noticed that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. 


UPDATE: I have changed the global durability setting to "max durability" from "perf optimized" and am still getting the same error.

timblaktu@gmail.com (JIRA)

unread,
Mar 5, 2020, 12:00:03 PM3/5/20
to jenkinsc...@googlegroups.com
Tim Black edited a comment on Bug JENKINS-60039
Reverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in an error due to an unmet dependency between Durable Task and Pipeline: Nodes and Processes. So I went back to DT v1.33 since I'm not immediately sure how to resolve this dependency heck.

In the meantime, I have noticed that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. 

UPDATE: I have changed the global durability setting to " max durability MAX_SURVIVABILITY " from "perf optimized" and am still getting the same error.

timblaktu@gmail.com (JIRA)

unread,
Mar 5, 2020, 12:01:03 PM3/5/20
to jenkinsc...@googlegroups.com
Tim Black edited a comment on Bug JENKINS-60039
Reverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in an error due to an unmet dependency between Durable Task and Pipeline: Nodes and Processes. So I went back to DT v1.33 since I'm not immediately sure how to resolve this dependency heck.

In the meantime, I have noticed that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. 

UPDATE: I have changed the global durability setting to "MAX_SURVIVABILITY" from " perf optimized PERFORMANCE_OPTIMIZED " and am still getting the same error.

timblaktu@gmail.com (JIRA)

unread,
Mar 5, 2020, 12:03:04 PM3/5/20
to jenkinsc...@googlegroups.com
Tim Black edited a comment on Bug JENKINS-60039
Reverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in an error due to an unmet dependency between Durable Task and Pipeline: Nodes and Processes. So I went back to DT v1.33 since a _lot_ of plugins depend on Nodes and Processes, and I'm not immediately sure how to resolve this dependency heck.


In the meantime, I have noticed that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. 

UPDATE: I have changed the global durability setting to "MAX_SURVIVABILITY" from "PERFORMANCE_OPTIMIZED" and am still getting the same error.

cchiou@cloudbees.com (JIRA)

unread,
Mar 5, 2020, 2:16:04 PM3/5/20
to jenkinsc...@googlegroups.com

Tim Black So the differences of 1.29 and 1.33 should be fairly negligible. What happened between all those release was the introduction of a binary wrapper (to replace the shell wrapper) for shell scripts to make them more "durable". However, there were varied compatibility issues (mostly with docker and non-x86 builds) that we made the original shell wrapper the default behavior again. Your logging shows that the original shell wrapper is indeed running. The biggest difference I can see between yours and the OP is that your script appears to be executing (writing output to the jenkins-log.txt) and terminating with 0 as opposed to failure.

Like I mentioned with OP, if you can run with LAUNCH_DIAGNOSTICS, that might help us get a better idea of what is going on.

timblaktu@gmail.com (JIRA)

unread,
Mar 11, 2020, 12:58:03 PM3/11/20
to jenkinsc...@googlegroups.com

For me, this issue turned out to be an empty environment variable set in Jenkins global properties. This. 
Reply all
Reply to author
Forward
0 new messages