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

Wrong autocompletion of node names with spaces

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • core

      Auto-complete is working wrong on nodes whith spaces in names. Or maybe it's just not compatible with the project configuration field "Restrict where this project can be run"; as this field expects the node name to be sourrounded by quotes
      see screenshots (on 3d one I've added the quotes manually)

        1. auto_complete_1.jpg
          auto_complete_1.jpg
          5 kB
        2. auto_complete_2.jpg
          auto_complete_2.jpg
          7 kB
        3. auto_complete_3.jpg
          auto_complete_3.jpg
          6 kB

          [JENKINS-14190] Wrong autocompletion of node names with spaces

          Daniel Beck added a comment -

          Reproduced on 1.567:

          Slave name: a b c
          Error: Invalid boolean expression: unexpected token: b

          Daniel Beck added a comment - Reproduced on 1.567: Slave name: a b c Error: Invalid boolean expression: unexpected token: b

          Catalin Poitasu added a comment -

          Seems to be fixed on Jenkins ver. 1.594.

          I created a slave with the name "a b c" and a project for which I added the restriction to that slave. While typing the name of the slave I got the suggestion "a b c" without the quotes. Pressing ENTER, the name of the slave without the quotes was added to the text field. After saving the configuration of the job, the label appeared with quotes, which is correct. Furthermore, every functionality related to this label could be verified:

          • the project was sent to the proper slave
          • the project was tied to the assigned slave, when opening the page of the slave

          So this is either fixed or it is something Jenkins handles automatically once the configuration page of the job is saved, since there was no need to add the quotes manually in the test.
          Using quotes make sense due to more complex constructions: e.g:
          user:... || role:... || "a b c"

          Catalin Poitasu added a comment - Seems to be fixed on Jenkins ver. 1.594. I created a slave with the name "a b c" and a project for which I added the restriction to that slave. While typing the name of the slave I got the suggestion "a b c" without the quotes. Pressing ENTER, the name of the slave without the quotes was added to the text field. After saving the configuration of the job, the label appeared with quotes, which is correct. Furthermore, every functionality related to this label could be verified: the project was sent to the proper slave the project was tied to the assigned slave, when opening the page of the slave So this is either fixed or it is something Jenkins handles automatically once the configuration page of the job is saved, since there was no need to add the quotes manually in the test. Using quotes make sense due to more complex constructions: e.g: user:... || role:... || "a b c"

            Unassigned Unassigned
            martan Martin Adam
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: