![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Honza Brázdil
|
|
Components:
|
ghprb |
|
Created:
|
02/Jul/13 10:18 AM
|
|
Description:
|
Currently, you configure a single API endpoint in the main Jenkins config. This effectively limits this incredibly useful plugin to only a single GitHub instance for all builds.
With GitHub Enterprise becoming increasingly popular, organizations are working with a mix of publicly hosted and internal projects.
Adding support for multiple GH endpoints would enable, at the job level, for us to choose which endpoint to use for a given job.
I'd define an endpoint as an API URL + credentials. I'm not sure how much value there would be in pulling all of the other values (admin lists, etc) into endpoint-specific properties as those seem like they'd apply to all endpoints equally.
I looked into contributing this functionality, but I confess that being new to Jenkins plugin authoring the way forward was unclear. For example, would endpoints become an property of the main task? How do you add repeaters for that property? Or would the entire main task become a repeatable?
Thanks for considering!
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Marc Esher
|
|
|
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
