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

Choice parameters not passed to P4 workspace / view

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • p4-plugin
    • Jenkins 1.488, Perforce plugin 1.3.17, 64-bit Windows OS, JRE 1.6.0.33, Tomcat 5.5

      [BTW, Thanks for your help and efforts with the P4 plugin. It is a fantastic tool!]

      Using a parameterized build I can set a string parameter X to a string value then reference ${X} in the Perforce workspace form where it resolves at build time to the value of ${X}.

      Alternately, using choice parameters (having pre-defined values) I set the value of X in the Perforce workspace form (or view) and it does not resolve the value, but rather passes it as a literal string: "${X}".

      The ability to resolve choice parameters seems to be a valuable functionality to have.

            Unassigned Unassigned
            tgreer Tom Greer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: