After the parameterized trigger plugin wants to exchange all choices to extensible choices we have to change many properties in our jobs. But that's OK.

      Problem:
      Because of many of our properties containing dots we have to overwork half of our build process.

      Suggestion:
      Please check if the name of a property can contain . too.


      Extensible Choice Parameter checks parameter names as Jenkins 1.466 expands variable
      (that is, alphabets, numbers, and underscore: https://github.com/jenkinsci/jenkins/blob/jenkins-1.466/core/src/main/java/hudson/Util.java#L111 )

      Jenkins 1.526 gets to allow dots in JENKINS-16660, f664639.

      Extensible Choice Parameter should check parameter names as the Jenkins core it runs on.

          [JENKINS-22222] Check variable names as Jenkins core expands

          Sven Appenrodt created issue -
          ikedam made changes -
          Link New: This issue is related to JENKINS-16660 [ JENKINS-16660 ]
          ikedam made changes -
          Assignee New: ikedam [ ikedam ]
          Description Original: After the parameterized trigger plugin wants to exchange all choices to extensible choices we have to change many properties in our jobs. But that's OK.

          Problem:
          Because of many of our properties containing dots we have to overwork half of our build process.

          Suggestion:
          Please check if the name of a property can contain . too.
          New: After the parameterized trigger plugin wants to exchange all choices to extensible choices we have to change many properties in our jobs. But that's OK.

          Problem:
          Because of many of our properties containing dots we have to overwork half of our build process.

          Suggestion:
          Please check if the name of a property can contain . too.

          ----

          Extensible Choice Parameter checks parameter names as Jenkins 1.466 expands variable
          (that is, alphabets, numbers, and underscore: https://github.com/jenkinsci/jenkins/blob/jenkins-1.466/core/src/main/java/hudson/Util.java#L111 )

          Jenkins 1.526 gets to allow dots in JENKINS-16660, [f664639|https://github.com/jenkinsci/jenkins/commit/f664639b79d2dea2abdf48816b01f8ccc525a73f].

          Extensible Choice Parameter should check parameter names as the Jenkins core it runs on.
          Issue Type Original: Task [ 3 ] New: Improvement [ 4 ]
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Summary Original: Extend name pattern to use dots too New: Check variable names as Jenkins core expands
          ikedam made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Sven Appenrodt made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 154302 ] New: JNJira + In-Review [ 207523 ]

            ikedam ikedam
            zioschild Sven Appenrodt
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: