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
1 file changed
tree: 8625ba3db3266f80b62bbbb21850620397cb1e12
  1. jenkins/
  2. jenkins-docker/
  3. .gitignore