Jenkins › Jenkins issues

[JIRA] (JENKINS-12217) xcode-plugin: fails to set default keychain when using alternate (non login) keychain

classic Classic list List threaded Threaded
♦
♦
 5 messages Options
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-12217) xcode-plugin: fails to set default keychain when using alternate (non login) keychain

JIRA noreply@jenkins-ci.org
David Whetstone created JENKINS-12217:
-----------------------------------------

             Summary: xcode-plugin: fails to set default keychain when using alternate (non login) keychain
                 Key: JENKINS-12217
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12217
             Project: Jenkins
          Issue Type: Bug
          Components: plugin, xcode
    Affects Versions: current
         Environment: Mac OS X 10.7.2
            Reporter: David Whetstone
            Priority: Blocker


Using the following settings:

  Unlock Keychain? checked
  Keychain path: ${HOME}/Library/Keychains/tout-iphone.keychain
  Keychain password: ******

The build fails with the error:

  Code Sign error: The identity 'iPhone Developer: XXXX XXXX (XXXX)' doesn't match any valid certificate/private key pair in the default keychain

In addition, once the build is complete, my login keychain is no longer present in the Keychain Access application.

I've tracked this down to XCodeBuilder.java:286

    268: launcher.launch().envs(envs).cmds("/usr/bin/security","login-keychain","-d","user",
            "-s",keychainPath).stdout(listener).pwd(projectRoot).join();

Specifically, it's calling 'security login-keychain' when I believe it should be calling 'security default-keychain'.  My build succeeds after changing this line to the following:

    268: launcher.launch().envs(envs).cmds("/usr/bin/security","default-keychain","-d","user",
            "-s",keychainPath).stdout(listener).pwd(projectRoot).join();

I haven't looked into how this affects configurations that don't specify an alternate keychain file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-12217) xcode-plugin: fails to set default keychain when using alternate (non login) keychain

JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

aheritier reassigned JENKINS-12217:
-----------------------------------

    Assignee: aheritier
   

> xcode-plugin: fails to set default keychain when using alternate (non login) keychain
> -------------------------------------------------------------------------------------
>
>                 Key: JENKINS-12217
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12217
>             Project: Jenkins
>          Issue Type: Bug
>          Components: plugin, xcode
>    Affects Versions: current
>         Environment: Mac OS X 10.7.2
>            Reporter: David Whetstone
>            Assignee: aheritier
>            Priority: Blocker
>
> Using the following settings:
>   Unlock Keychain? checked
>   Keychain path: ${HOME}/Library/Keychains/tout-iphone.keychain
>   Keychain password: ******
> The build fails with the error:
>   Code Sign error: The identity 'iPhone Developer: XXXX XXXX (XXXX)' doesn't match any valid certificate/private key pair in the default keychain
> In addition, once the build is complete, my login keychain is no longer present in the Keychain Access application.
> I've tracked this down to XCodeBuilder.java:286
>     268: launcher.launch().envs(envs).cmds("/usr/bin/security","login-keychain","-d","user",
>             "-s",keychainPath).stdout(listener).pwd(projectRoot).join();
> Specifically, it's calling 'security login-keychain' when I believe it should be calling 'security default-keychain'.  My build succeeds after changing this line to the following:
>     268: launcher.launch().envs(envs).cmds("/usr/bin/security","default-keychain","-d","user",
>             "-s",keychainPath).stdout(listener).pwd(projectRoot).join();
> I haven't looked into how this affects configurations that don't specify an alternate keychain file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-12217) xcode-plugin: fails to set default keychain when using alternate (non login) keychain

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157090#comment-157090 ]

aheritier commented on JENKINS-12217:
-------------------------------------

ok. Thx for your feedback. I will investigate more to understand the cause of the issue.
You'll have probably right about the wrong command call
               

> xcode-plugin: fails to set default keychain when using alternate (non login) keychain
> -------------------------------------------------------------------------------------
>
>                 Key: JENKINS-12217
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12217
>             Project: Jenkins
>          Issue Type: Bug
>          Components: plugin, xcode
>    Affects Versions: current
>         Environment: Mac OS X 10.7.2
>            Reporter: David Whetstone
>            Assignee: aheritier
>            Priority: Blocker
>
> Using the following settings:
>   Unlock Keychain? checked
>   Keychain path: ${HOME}/Library/Keychains/tout-iphone.keychain
>   Keychain password: ******
> The build fails with the error:
>   Code Sign error: The identity 'iPhone Developer: XXXX XXXX (XXXX)' doesn't match any valid certificate/private key pair in the default keychain
> In addition, once the build is complete, my login keychain is no longer present in the Keychain Access application.
> I've tracked this down to XCodeBuilder.java:286
>     268: launcher.launch().envs(envs).cmds("/usr/bin/security","login-keychain","-d","user",
>             "-s",keychainPath).stdout(listener).pwd(projectRoot).join();
> Specifically, it's calling 'security login-keychain' when I believe it should be calling 'security default-keychain'.  My build succeeds after changing this line to the following:
>     268: launcher.launch().envs(envs).cmds("/usr/bin/security","default-keychain","-d","user",
>             "-s",keychainPath).stdout(listener).pwd(projectRoot).join();
> I haven't looked into how this affects configurations that don't specify an alternate keychain file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-12217) xcode-plugin: fails to set default keychain when using alternate (non login) keychain

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

aheritier resolved JENKINS-12217.
---------------------------------

    Resolution: Fixed

Will be fixed in version 1.3
               

> xcode-plugin: fails to set default keychain when using alternate (non login) keychain
> -------------------------------------------------------------------------------------
>
>                 Key: JENKINS-12217
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12217
>             Project: Jenkins
>          Issue Type: Bug
>          Components: plugin, xcode
>    Affects Versions: current
>         Environment: Mac OS X 10.7.2
>            Reporter: David Whetstone
>            Assignee: aheritier
>            Priority: Blocker
>
> Using the following settings:
>   Unlock Keychain? checked
>   Keychain path: ${HOME}/Library/Keychains/tout-iphone.keychain
>   Keychain password: ******
> The build fails with the error:
>   Code Sign error: The identity 'iPhone Developer: XXXX XXXX (XXXX)' doesn't match any valid certificate/private key pair in the default keychain
> In addition, once the build is complete, my login keychain is no longer present in the Keychain Access application.
> I've tracked this down to XCodeBuilder.java:286
>     268: launcher.launch().envs(envs).cmds("/usr/bin/security","login-keychain","-d","user",
>             "-s",keychainPath).stdout(listener).pwd(projectRoot).join();
> Specifically, it's calling 'security login-keychain' when I believe it should be calling 'security default-keychain'.  My build succeeds after changing this line to the following:
>     268: launcher.launch().envs(envs).cmds("/usr/bin/security","default-keychain","-d","user",
>             "-s",keychainPath).stdout(listener).pwd(projectRoot).join();
> I haven't looked into how this affects configurations that don't specify an alternate keychain file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-12217) xcode-plugin: fails to set default keychain when using alternate (non login) keychain

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arnaud Héritier closed JENKINS-12217.
-------------------------------------

   

> xcode-plugin: fails to set default keychain when using alternate (non login) keychain
> -------------------------------------------------------------------------------------
>
>                 Key: JENKINS-12217
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12217
>             Project: Jenkins
>          Issue Type: Bug
>          Components: plugin, xcode
>    Affects Versions: current
>         Environment: Mac OS X 10.7.2
>            Reporter: David Whetstone
>            Assignee: Arnaud Héritier
>            Priority: Blocker
>
> Using the following settings:
>   Unlock Keychain? checked
>   Keychain path: ${HOME}/Library/Keychains/tout-iphone.keychain
>   Keychain password: ******
> The build fails with the error:
>   Code Sign error: The identity 'iPhone Developer: XXXX XXXX (XXXX)' doesn't match any valid certificate/private key pair in the default keychain
> In addition, once the build is complete, my login keychain is no longer present in the Keychain Access application.
> I've tracked this down to XCodeBuilder.java:286
>     268: launcher.launch().envs(envs).cmds("/usr/bin/security","login-keychain","-d","user",
>             "-s",keychainPath).stdout(listener).pwd(projectRoot).join();
> Specifically, it's calling 'security login-keychain' when I believe it should be calling 'security default-keychain'.  My build succeeds after changing this line to the following:
>     268: launcher.launch().envs(envs).cmds("/usr/bin/security","default-keychain","-d","user",
>             "-s",keychainPath).stdout(listener).pwd(projectRoot).join();
> I haven't looked into how this affects configurations that don't specify an alternate keychain file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Loading...
Powered by Nabble See how NAML generates this page