[JIRA] (JENKINS-13887) Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build

John Grattan created JENKINS-13887:
--------------------------------------

             Summary: Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build
                 Key: JENKINS-13887
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13887
             Project: Jenkins
          Issue Type: New Feature
          Components: xcode
            Reporter: John Grattan
            Priority: Minor


Similar to the Technical Version Number (CFBundleVersion), it would be nice to have an option to change the Bundle identifier (CFBundleIdentifier).

--
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

       

Rowan James commented on JENKINS-13887

Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build

This would be a great assist to me; setting a distinct bundle identifier lets a built iPhone app install side-by-side with another build of the same project.

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

Mark Warren commented on JENKINS-13887

Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build

I concur. I'm currently trying to use a shell command prior to the Xcode plugin to set the CFBundleIdentifier value: defaults write ${WORKSPACE}/Targetname-Info CFBundleIdentifier com.mycompany.mycompany However, this results in a build error: The following build commands failed: ProcessInfoPlistFile /Users/Jenkins/workspace/MyApp/builds/MyApp.app/Info.plist Targetname-Info.plist (1 failure) Build step 'XCode' marked build as failure I'm trying to figure out what is going on there, looks like something is messing up the file somehow.

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