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

ant issues on empty build parameters

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Component/s: core
    • Labels:
      None
    • Environment:
      at least windows
    • Similar Issues:

      Description

      When one set a build parameter to an empty value, ant build steps end up with a broken command line. I can't see what happens with the command line exactly but seems like the next build parameter ends up as a value to the -D<param>=

      One would want to have such setup for example with the JAVA_OPTS environment variable. It would normally be unset but set to some value for debugging purposes or depending on the slave the build is executing on.

      Of course workarounds exist but parameters are a great convenience.

        Attachments

          Issue Links

            Activity

            akostadinov akostadinov created issue -
            abayer Andrew Bayer made changes -
            Field Original Value New Value
            Link This issue duplicates JENKINS-7204 [ JENKINS-7204 ]
            abayer Andrew Bayer made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Duplicate [ 3 ]
            ircbot Jenkins IRC Bot made changes -
            Component/s core [ 15593 ]
            Component/s parameters [ 15594 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 135243 ] JNJira + In-Review [ 186949 ]

              People

              • Assignee:
                huybrechts huybrechts
                Reporter:
                akostadinov akostadinov
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: