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

Pipelines will misbehave if some special symbols are given in the name

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • blueocean-plugin
    • \My client is a Manjaro Linux install, kernel version 4.4.54-1. The browsers I tested this with are: Firefox 52.0 (64-bit), and Chromium 57.0.2987.110 (64-bit)

      Problem: The pipeline creation wizard in BO does not check for special characters and does not redirect to the activity page of jobs with special characters.

      The same constraints/rules should apply as in classic

      Care must be taken to ensure valid unicode is allowed and not inadvertently blocked. ATH test coverage is a pre-req for this. 

      Steps to reproduce:

      1. Create a new pipeline using the BO UI
      2. In the pipeline name field enter any of these:
      3. file:/etc/hosts
      4. Or any of the unicode special characters from here:  https://github.com/minimaxir/big-list-of-naughty-strings/blob/master/blns.txt
      1. Save the pipeline.
      2. At this point I got a 404
      3. Next I saw that the job was in the main UI but which I clicked on it, I got another 404.
      4. After I restated the jobs with the special characters disappeared from the UI.

          [JENKINS-42990] Pipelines will misbehave if some special symbols are given in the name

          Michael Neale added a comment - - edited

          Needs more investigation

          • firstly the validation should be the same as Jenkins classic
          • with valid characters allowed by classic, pipeline creation should still work

           

          This may end up as 2 tickets

           

          EDIT: I checked some different languages that are legitimate and it works correctly, so this ticked is valid in requiring more validation

           

          Michael Neale added a comment - - edited Needs more investigation firstly the validation should be the same as Jenkins classic with valid characters allowed by classic, pipeline creation should still work   This may end up as 2 tickets   EDIT: I checked some different languages that are legitimate and it works correctly, so this ticked is valid in requiring more validation  

          Gavin Mogan added a comment -

          I'm going to close this for now, i don't know if its been fixed, but the pipeline creation UI doesn't ask for a name

          Gavin Mogan added a comment - I'm going to close this for now, i don't know if its been fixed, but the pipeline creation UI doesn't ask for a name

            Unassigned Unassigned
            zjoyner Zachary Joyner
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: