Jobname with single quote breaks pipeline sh command

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

XMLWordPrintable

      Using a backtick in the Job name does not work together with the sh command in a pipeline.
      E.g. a pipeline job with the name "Developer Test" and the following pipeline script

      node{
      sh 'echo "hello world"'
      }
      

      will print "hello world".

      Changing the name of the Job to "Developer's Test" (or any other name with a single backtick) breaks the build and fails with "ERROR: script returned exit code -2".

      I would expect a more expressive error message in the pipeline or a check to forbid such characters in the job name.

            Assignee:
            Unassigned
            Reporter:
            Daniel Haftstein
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: