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

Wrong escaping of quotes in git summary parameter for ant

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      os.name Windows Server 2008 R2
      jenkins 2.19
      ant 1.3
      gerrit-trigger 2.22.0
      git 2.5.3
      git-client 1.21.0
      git-server 1.7
    • Similar Issues:

      Description

      When using quotes in a git commit summary, all ant build fail due to wrong escaping.
      Ant then wrongly interprets parts of the commit summary as an ant target, which does not exist.

      Since the parameters are somehow forced on me by, idk - the git-plugin? i dont see a way to fix it myself, even though i dont even need the commit summary in my ant scripts.

      See the attached screenshot for the commit details and build output.

      thank you & best regards,
      keydon

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          I don't understand how to duplicate the problem you're reporting. Based on the description and guesses from the screen shot, I assume you're using the gerrit trigger plugin and running an ant build step within your job.

          The git plugin does not modify build steps, so it seems quite unlikely that the parameters are a result of the git plugin.

          Show
          markewaite Mark Waite added a comment - I don't understand how to duplicate the problem you're reporting. Based on the description and guesses from the screen shot, I assume you're using the gerrit trigger plugin and running an ant build step within your job. The git plugin does not modify build steps, so it seems quite unlikely that the parameters are a result of the git plugin.
          Hide
          keydon Lukas Bugaj added a comment -

          I think you are correct Mark Waite. In retrospect the git-plugin is indeed unlikely responsible for those additional parameters.
          Now i think its the gerrit-trigger-plugin.

          My setup is quite simple, its a gerrit verfication build with one build step, an ant-script.
          It has a gerrit-event-listener listening on particular branches.

          So i guess the git-trigger-plugin gets those parameters from gerrit and then injects it to the ant-build-step.

          Show
          keydon Lukas Bugaj added a comment - I think you are correct Mark Waite . In retrospect the git-plugin is indeed unlikely responsible for those additional parameters. Now i think its the gerrit-trigger-plugin. My setup is quite simple, its a gerrit verfication build with one build step, an ant-script. It has a gerrit-event-listener listening on particular branches. So i guess the git-trigger-plugin gets those parameters from gerrit and then injects it to the ant-build-step.

            People

            • Assignee:
              armfergom Armando Fernandez
              Reporter:
              keydon Lukas Bugaj
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: