Apostrohe in Job name causes sh based steps to hang

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      In pipe line jobs, if the name of the job has an apostrophe in it, and a sh step is executed, the job will hang for awhile then eventually fail.  This occurs with regular sh steps and other sh backed steps like the docker plugin steps.

       

      Example Job :

      Sh'BreaksJob

       

      Script:

       

      pipeline {
        agent any
        stages {
         stage('Hello') {
           steps {
               sh 'echo "hello world"'
            }
          }
        }
      }
      

       

       

      Output

       
      Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/workspace/Testing/Sh'BreaksJob[Pipeline] {[Pipeline] stage[Pipeline]

      { (Hello)[Pipeline] shprocess apparently never started in /var/lib/jenkins/workspace/Testing/Sh'BreaksJob@tmp/durable-91bcd577 (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)[Pipeline] }

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

            Assignee:
            Unassigned
            Reporter:
            Jonathon Lamon
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: