Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-67884

Using ${variable} in pipeline results in ERR_CONNECTION_RESET

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • None
    • Docker LTS Jenkins 2.319.3

      Since upgrading to the latest LTS (and after multiple plugin updates) jobs that use variables like ${variable} instead of $variable can't be saved anymore.

      Clicking save will result in a ERR_CONNECTION_RESET.

      Also, unchecking "Use Groovy Sandbox" will result in a "An internal error occured during form validation (HTTP 0)" underneath the pipeline script text box. (See images)

      Changing variables to $variable lets the jobs be saved.

      Existing jobs with the ${variable} syntax are still able to run but not modified.

        1. image (4).png
          image (4).png
          304 kB
        2. image (5).png
          image (5).png
          520 kB
        3. screenshot-1.png
          screenshot-1.png
          8 kB

            Unassigned Unassigned
            channyboy CHANNY
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: