Do not SPAM the change with jobs queued messages
When a build is scheduled for a change under verification
it is risky to generated a "Verfication queued" message because
we do not know upfront if the verification flow will ever succeed
or not.
Multiple retries of building the same change would then result
in excessive SPAMming of the target change. It is much better
to limit the noise on the target change and provide feedback
only when we are sure about the final verdict of the verification
flow.
Change-Id: I8ccc73bad5458c3f88a5029dc2b798a15a9a56f3
diff --git a/jenkins/gerrit-verifier-change.groovy b/jenkins/gerrit-verifier-change.groovy
index bcb7345..9d50e99 100644
--- a/jenkins/gerrit-verifier-change.groovy
+++ b/jenkins/gerrit-verifier-change.groovy
@@ -384,7 +384,6 @@
if(sha1 == null) {
println "[WARNING] Skipping change " + changeJson.change_id + " because it does not have any current revision or patch-set"
} else {
- gerritComment(build.startJob.getBuildUrl() + "console",changeJson._number,changeJson.current_revision,"Verification queued on")
buildChange(changeJson)
}
