[JENKINS-22473] GERRIT_CHANGE_SUBJECT value not updated after first patch set

Accidentally added a back quote '`' to the subject of the commit and it broke Jenkins build "/usr/bin/ant: 1: eval: Syntax error: EOF in backquote substitution".

Uploaded second patch set without back quote but fails because GERRIT_CHANGE_SUBJECT is stuck on the old value. I'm able to apply the change locally and verified the back quote is not present and can see from the Jenkins logs that it is using the second patch set except GERRIT_CHANGE_SUBJECT value is not correct.

Forced to abandon my change and re-upload as a separate code review.

---
Originally reported by kevin_brotcke, imported from: GERRIT_CHANGE_SUBJECT value not updated after first patch set

• assignee: rsandell
  
• status: Open
  
• priority: Minor
  
• component(s): gerrit-trigger-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 2025-12-06
  

Raw content of original issue

Accidentally added a back quote '`' to the subject of the commit and it broke Jenkins build "/usr/bin/ant: 1: eval: Syntax error: EOF in backquote substitution".


Uploaded second patch set without back quote but fails because GERRIT_CHANGE_SUBJECT is stuck on the old value. I'm able to apply the change locally and verified the back quote is not present and can see from the Jenkins logs that it is using the second patch set except GERRIT_CHANGE_SUBJECT value is not correct.


Forced to abandon my change and re-upload as a separate code review.

environment

```
Jenkins ver. 1.532.1

Gerrit Trigger 2.11.0

Gerrit Code Review (2.1.7)
```

Start by reproducing the reported behavior with two Gerrit patch sets, using the Jenkins logs and the GERRIT_CHANGE_SUBJECT environment value described in the issue. Trace the Gerrit Trigger plugin's patch-set handling; the work is done when the variable reflects the latest patch-set subject, including removal of the back quote.

Written by the indexing model from the issue text.