Hello,
I am making a pass at the xcode-plugin these days. I am going through the pull requests and issues and trying to put a bit of order in the plugin.
One particular issue is the management of keychains, which can be done in different ways.
Right now we have:
1. global keychains
2. job keychains
3. developerProfile loading (into custom keychains)
I really like the developerProfile one. They fit well in the jenkins credentials mechanism.
A better way IMHO would be to relock automatically the keychain once not needed (at least for those we know aren't shared simultaneously by multiple jobs). That really sounds like a BuildWrapper to me.
Koshuke, is this what you had in mind when adding the:
* TODO: destroy identity in the end.
Has anyone tip on how could this be implemented in a nice way ? (I looked a bit at the Lock and Latches plugin).
Another issue is that the global and job keychain mechanisms have several issues:
* they store passwords in plaintext. So that's not good.
* also their they require configuration to be done before hand on all machines. Not practical for slaves setup
* finally I suspect that the granularity of only having global or job keychains make them not very useful in the case of having servers with compartmented teams
And there are probably other problems I don't know of. I am almost in favor of deprecating this mechanism and not supporting them anymore and let people use custom scripts to extend this functionality instead. Any feedback on this idea ?
Thanks,
Jerome