![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Unassigned |
|
Components:
|
kpp-management |
|
Created:
|
02/Oct/14 8:22 PM
|
|
Description:
|
Put simply, if there's a use-case for not overwriting the keychain, it's far outnumbered by the use-cases where the job should overwrite the keychain. Not overwriting the keychain with the new one effectively stops the job from getting any certificate updates, which causes more problems than it solves.
If there really is a need for this feature, it should be marked with a warning that this behavior is not the norm.
Deleting the keychain after build creates unexpected behavior because of a defect in xcode-plugin. Hard to explain, but it has to do with how xcodeplugin keeps track of which keychain is the current keychain.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Tom Jones
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
