Re:Commit access for new jenkins plugin: Keychains and Provisioning Profiles Management

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

Could this be implemented on top of the Credentials plugin, rather than standalone?

----- Original Message -----
From: jenkin...@googlegroups.com
To: jenkin...@googlegroups.com
At: Aug 2 2013 06:31:33

Hi,

I have written a Jenkins plugin to manage keychains and provisioning profiles for iOS and OSX build jobs via Jenkins.

Please fork this github repo: https://github.com/SICSoftwareGmbH/kpp-management-plugin 

Wiki page: http://wiki.jenkins-ci.org/display/JENKINS/Keychains+and+Provisioning+Profiles+Plugin

My github username: michaelbaer

Thanks,

Michael

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Michael Bär]

I am not sure if the functionality of the Credentials plugin is sufficient to mange this.

1. Keychain
1. Support file upload.
2. Could have a password.
3. Could have a description.
4. Could include manually added multiple code signing identities.
5. To integrate a keychain into a build job:
1. Select the keychain.
2. Select the code signing identity.
3. Three environment variables are set:
1. The path of the keychain copied on the node, where the build job is executed.
2. The general name of the selected code signing identity.
3. The password to unlock the keychain.
2. Provisioning Profiles
1. They are separated from keychains.
2. Support file upload.
3. They are no real credentials.
4. To integrate a provisioning profile into a build job:
1. Select the provisioning profile.
2. Set the uuid of the provisioning profile as an environment variable.

[Stephen Connolly]

On 5 August 2013 17:33, Michael Bär <michael....@googlemail.com> wrote:

I am not sure if the functionality of the Credentials plugin is sufficient to mange this.

1. Keychain
1. Support file upload.
2. Could have a password.
3. Could have a description.
4. Could include manually added multiple code signing identities.
5. To integrate a keychain into a build job:
1. Select the keychain.
2. Select the code signing identity.
3. Three environment variables are set:
1. The path of the keychain copied on the node, where the build job is executed.
2. The general name of the selected code signing identity.
3. The password to unlock the keychain.

I think the above could be integrated with the Credentials plugin. 

1. You would need to decide at what level to integrate: either the entire keychain is a credential, or the identities that are added to the keychain are credentials. I would favour the entire keychain... but the UI could be fun to construct. Supporting file upload is not a blocker BTW.