|
||||||||
|
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.
Right I do nothing hence the reason for not pushing. I suspect that if we want to provide keychain management, we need to properly implement
Maybe there should be one module that deals with the keychain.
And then another one that deals with xcode. The first one would find a way to tell the xcode one which keychain to use.
I am unsure of the implementation given the different solutions today.
This requires some changes (probably have a buildwrapper or whatever this is called in the jenkins world).
I would prefer some consensus first![]()