Open Radar

 
Summary:
Scenario:
The goal is to create a daily build using Xcode bots for iOS and Mac projects. To be able to identify individual builds we need to provide unique (and increasing) values for CFBundleVersion.

Problem:
One common approach is add a "Post-action" for the "Archive" in the used scheme and patch the `info.plist` of the generated app bundles and also the generated dSYM packages. This is only working if all created targets are actually app bundles and not command line executables (Mac platform) which need the info.plist data to be embedded into the executable. So this is NOT working for command line executables which are build as part of the main app project as dependencies.

Feature Request:
Provide a "Pre-everything" section where developers can add scripts or other functionalities just like in the usual "Pre-actions" or "Post-actions" for "Build", "Test", "Archive", etc. This should run before "xcodebuild" is called and any files are being read.
Als provide a "Post-everything" section where developers can the same as above.

Benefit:
The developer could define a "Pre-everything" action with a script that patches an Info.plist or any other file adjusting the version number. Then the archive process would be executed and all targets could use the same CFBundleVersion. In a "Post-everything" action the developer could do a cleanup on the patched files reverting the changes or e.g. call "git reset --hard" so the checked out repository won't be dirty.