Having Gerritt updated with the QB build status every time a build is triggered with a QB Gerritt Repository causes Gerritt to generate a large number of emails for each build. We have a large organization, and Gerritt is set up to send an email to the submitter and all reviewers each time there is an update to Gerritt. Thus, dozens of emails are generated by Gerritt with each QB build. This causes nothing short of panic with the developers and reviewers.
Please add a check box or some other option to 'Disable Gerritt Updates', or something similar, within the QB Gerritt Repository.
Thanks.
Description
Having Gerritt updated with the QB build status every time a build is triggered with a QB Gerritt Repository causes Gerritt to generate a large number of emails for each build. We have a large organization, and Gerritt is set up to send an email to the submitter and all reviewers each time there is an update to Gerritt. Thus, dozens of emails are generated by Gerritt with each QB build. This causes nothing short of panic with the developers and reviewers.
Please add a check box or some other option to 'Disable Gerritt Updates', or something similar, within the QB Gerritt Repository.
Thanks.