-
Improvement
-
Resolution: Unresolved
-
Major
-
None
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.
- is related to
-
JENKINS-10984 Truncating GERRIT_CHANGE_SUBJECT can prevent maven from running
- Open
-
JENKINS-11779 Gerrit-plugin modifies ant command line which is not compatible on windows
- Open