![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
rsandell
|
|
Components:
|
gerrit-trigger-plugin |
|
Created:
|
09/Apr/15 8:29 PM
|
|
Description:
|
Use case: Gerrit support custom labels. We would like to use such labels in combination with Code Review and Verified to track all phases of a given change through Gerrit e.g. labels for Build, Install, Package, Test, and have the Jenkins jobs triggered accordingly. Today this not possible given Gerrit trigger does not support custom labels (the job flow can of course be implemented other ways, pipeline, etc). By editing the verified commands we can change what verified and code review in Jenkins means in Gerrit, but this seems at server and not job level, so does not solve the issue.
Requirements: it shall be possible to
- Define custom labels per Gerrit server (global configuration)
- Configure custom labels per job
- Same functionality for custom label as Code Review and Verified i.e. set custom label according to single or multiple jobs triggered by same patchset
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Christian Lague
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
