|
||||||||
|
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/d/optout.
Nicolas I agree.
I am hoping to get time to work on an enhancement that uses the Credentials plugin - this means that multiple credentials can be stored centrally - and then you can pick one per job.
emails/username/password and server can be stored as part of the named credential - then on each job you could pick from a drop down (perhaps with a default?) which credential (and thus which registry) to use.
I am just a bit lost on how to implement things with credentials (custom ones) so have asked for help. If you know anything or want to have a crack - by all means please do!
(not critical for me either but moving to the credentials plugin I think is pretty important - so why not allow multiple registries per step- think of it like git - you can pick credential at the time you put in in your repo).