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

Ant plugin regression between release 1.642.4 ant 1.651.1

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • ant-plugin
    • None

      when a parameter is empty, the task failed

      Job OK (1.642.4)
      [piil-ant-tests] $ cmd.exe /C '"C:\Tools\ant\apache-ant-1.9.4\bin\ant.bat -file piil_ant_tests_ext-deploy_release.xml -DPAT_INSTRUMENTED_WORKSPACE="" deploy_release -v && exit %%ERRORLEVEL%%"'

      Job NOK (1.651.1):
      [piil-ant-tests] $ cmd.exe /C "C:\Tools\ant\apache-ant-1.9.4\bin\ant.bat -file piil_ant_tests_ext-deploy_release.xml -DPAT_INSTRUMENTED_WORKSPACE= deploy_release -v && exit %%ERRORLEVEL%%"

          [JENKINS-34325] Ant plugin regression between release 1.642.4 ant 1.651.1

          Kenny Wang added a comment -

          We have the exact same issue. Jobs work fine in LTS1.642.4. They failed after upgrading to LTS 1.651.1

          A temporary work around is to set the value of string parameter to be '' (2 single quotes) instead of leaving it empty.

          Kenny Wang added a comment - We have the exact same issue. Jobs work fine in LTS1.642.4. They failed after upgrading to LTS 1.651.1 A temporary work around is to set the value of string parameter to be '' (2 single quotes) instead of leaving it empty.

          I am trying to reproduce the issue but I am not able to. I am using Ant Plugin 1.2, and Jenkins 1.651.1.

          I have a task in my test build.xml:

          <echo>Parameter: ${customParameter}</echo>
          

          I can use both

          customParameter= and customParameter="" in the Properties field with no issue. sorutome plegoff Could you please elaborate on how to reproduce the issue? I am happy to investigate this if I am able to reproduce.

          Armando Fernandez added a comment - I am trying to reproduce the issue but I am not able to. I am using Ant Plugin 1.2, and Jenkins 1.651.1. I have a task in my test build.xml: <echo>Parameter: ${customParameter}</echo> I can use both customParameter= and customParameter="" in the Properties field with no issue. sorutome plegoff Could you please elaborate on how to reproduce the issue? I am happy to investigate this if I am able to reproduce.

          Ralph Magnus added a comment -

          I can reproduce this issue with both installations LTS 1.651.1 and 2.1 on Windows Server 2008 R2. Maybe it's a specific issue with Windows OS only ..?

          Ralph Magnus added a comment - I can reproduce this issue with both installations LTS 1.651.1 and 2.1 on Windows Server 2008 R2. Maybe it's a specific issue with Windows OS only ..?

          I was able to reproduce this on Windows and after some investigation, noticed that there is already a PR for this. Also, this ticket is duplicated by JENKINS-33712 so I guess this can be closed. I will leave that up to the maintainer.

          Armando Fernandez added a comment - I was able to reproduce this on Windows and after some investigation, noticed that there is already a PR for this. Also, this ticket is duplicated by JENKINS-33712 so I guess this can be closed. I will leave that up to the maintainer.

          plegoff This has been resolved in version 1.3. Please, could you confirm it works so that I can close the issue?

          Armando Fernandez added a comment - plegoff This has been resolved in version 1.3. Please, could you confirm it works so that I can close the issue?

          Hi amando,
          it's ok now
          best regards

          Pascal Le Goff added a comment - Hi amando, it's ok now best regards

            armfergom Armando Fernandez
            plegoff Pascal Le Goff
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: