commit | 2e93e4e677b39ecd32936658e3c4f9fa9258b04b | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Thu Dec 30 10:29:38 2021 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Tue Jan 04 12:02:38 2022 -0600 |
tree | 7008e7f72e562acd2bcb244f7d5cb259472b04d7 | |
parent | 0ea75ec9efb7ffacb88f63e38fa7823fe8b124a7 [diff] |
userid-validation: erase score after trigger The newer versions of Gerrit seem to send events that include the "Ok-To-Test=1" score on future comments by Jenkins itself. This can cause Jenkins to infinite loop itself by seeing its own "Validated=1" comment _with_ an "Ok-To-Test=1" inside it. There isn't much capability to filter this out in the Jenkins Gerrit Trigger Plugin. Attempt to work around it by adding immediately erasing the Jenkins Ok-To-Test score. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I93525b4d8ba7321a5669da4e0296a62cc342fb76
Build script for CI jobs in Jenkins.