|
||||||||
|
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.
Here are my findings so far:
1- if we don't specify the -configuration argument, as the plugin doesn't try to infer xcodebuild defaults configuration for the command line, the plugin creates an invalid buildDirectory
2- we could try to extract this information from the project/workspace, but I haven't managed to get xcodebuild to behave as it says it should when building a project without specifying the configuration (I mailed the xcode-users list about it for clarification, the conversation will appear on http://lists.apple.com/archives/xcode-users/2014/Dec/index.html)
3- if you don't specify the BUILD_CONFIGURATION_DIR, xcode will build under some temporary directory that isn't under jenkins workspace (DerivedData etc). So even if jenkins created (mkdir) the missing default directory given "default configuration (infered) + buildPlatform" it isn't searching for the build apps under the right directory
List<FilePath> apps = buildDirectory.list(new AppFileFilter());
4- the ipa directory will be under the build configuration dir
I have to think about it more, but I think the simplest is to force the user to specify the BUILD_CONFIGURATION_DIR when selecting the generate IPA option or provide a good default. I am not sure why the other case (let xcode use his own DerivedData dirs) would be useful.