kingargyle created JENKINS-13216:
------------------------------------
Summary: Allow Triggers on Custom Labels
Key: JENKINS-13216
URL: https://issues.jenkins-ci.org/browse/JENKINS-13216
Project: Jenkins
Issue Type: New Feature
Components: gerrit-trigger
Reporter: kingargyle
Assignee: rsandell
Currently gerrit-trigger happens when the code is submitted for review. This
automatically triggers a build. There are use cases where it may not be
desirable to trigger the build until after at least one person has +1 or set a
custom label to a +1 value (i.e. Initial Security Review Completed: +1). This
would then allow a person to take a quick look at something, and then let the
workflow build the change after a cursory glance at the code.
The rest of the gerrit-trigger process could then flow through (i.e. set
verified, or set the custom label.).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
