The application that requires access to your private key is “/usr/bin/codesign”
if you don’t want to grant wildcard access to your private key. If you’re doing
any simulator orchestration then you will also want to be sure that the user
logged into the CI agent is the same user Jenkins is runnin
y, March 7, 2012 3:50:32 PM UTC-7, Elkin, Michael wrote:
The problem is that keychains need to be unlocked to access the contents of it,
and also that codesign is an untrusted application requesting access to a
private key. You need to add /usr/bin/codesign as a trusted application to the
private k
The problem is that keychains need to be unlocked to access the contents of it,
and also that codesign is an untrusted application requesting access to a
private key. You need to add /usr/bin/codesign as a trusted application to the
private key via the following steps:
1) Login to the system wh
If you have well-named jobs, you can try the role-based plug-in which has
regular expressions and may be easier to test/deploy/manage:
https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of E
