[JENKINS-10692] Mke it possible to not supply GERRIT_CHANGE_SUBJECT variable to build command lines.

Whilst it may be nice to have the GERRIT_* variables exposed to ant and maven builds - it is not used/required (at least by us).

This causes fluff in the console log - and in the worst cases causes the builds to fail as the escaping is not right for all the cases (and I'm not sure it can ever be right for all use cases).

Hence there should be a way to just tell the gerrit trigger to not expose these parameters to the build - just the bare minimum to get the git plugin to build the correct change.

---
Originally reported by teilo, imported from: Mke it possible to not supply GERRIT_CHANGE_SUBJECT variable to build command lines.

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

Whilst it may be nice to have the GERRIT_* variables exposed to ant and maven builds - it is not used/required (at least by us).


This causes fluff in the console log - and in the worst cases causes the builds to fail as the escaping is not right for all the cases (and I'm not sure it can ever be right for all use cases).


Hence there should be a way to just tell the gerrit trigger to not expose these  parameters to the build - just the bare minimum to get the git plugin to build the correct change.

Start by tracing how the gerrit-trigger-plugin exposes GERRIT_* variables to Ant and Maven build command lines, and how the Git plugin receives the values needed to build the correct change. Done means users can disable the extra variables while retaining the minimum required for the Git plugin, with escaping-related failures avoided.

Written by the indexing model from the issue text.