jenkinsci / jenkinsci/gerrit-trigger-plugin
[JENKINS-37827] Wrong escaping of quotes in git summary parameter for ant
- Dominant language
- Java
- Stars
- 226
- Forks
- 289
- PR merge metrics
- No merged PRs in 30d
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
---
Originally reported by keydon, imported from: Wrong escaping of quotes in git summary parameter for ant
armfergom
Raw content of original issue
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
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
```
2 attachments
- [escaping-gone-wrong.jpg](https://issues.jenkins.io/secure/attachment/33772/escaping-gone-wrong.jpg)
> 
- [git-param-overview.jpg](https://issues.jenkins.io/secure/attachment/33773/git-param-overview.jpg)
> 
Contributor guide
Research direction
No source files or tests are identified in the issue. Reproduce a Gerrit-triggered Ant build using a Git commit summary containing quotes, then trace how the summary becomes a build parameter. Done means quoted summaries no longer cause Ant to interpret part of the summary as a nonexistent target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100