![]() Xcode Cloud assigns a build number to each build it performs If you opt to add the TestFlight Internal Testing post-action, you're also required to check the Restrict Editing flag in the General tab as seen below. ![]() I'd suggest configuring the Notify action, This will notify you ( via email or slack ) when your workflow has either completed successfully or failed.Īdditionally, my interest was to have the app distributed to my TestFlight Internal Testing team once successfully built on Xcode Code. Note: Setting the Deployment Preparation to TestFlight and App Store, requires the clean flag in the Environment tab to be checked as seen below. My goal was to use Xcode Cloud to archive and distribute my app to TestFlight for internal / external testing. In the Branch Changes tab, set Files and Folders to Custom Conditions then configure as seen in the image below: Within Xcode, Product > Xcode Cloud > Create Workflow | Manage Workflowsįor a flutter app, it's reasonable that you'd want Xcode Cloud to trigger a new build after you've pushed commits with changes to either pubspec.yaml, lib/ or ios/. PS: In the tests I've ran, this script adds roughly ~10 mins to the total build duration, immensely longer than it even takes to archive the app ( ~ 5 mins ) Workflow Configuration Git add ios/ci_scripts/ci_post_clone.sh -chmod=+x #!/bin/sh # by default, the execution directory of this script is the ci_scripts directory # CI_WORKSPACE is the directory of your cloned repo echo "□ Navigate from ( $PWD) to ( $CI_WORKSPACE) " cd $CI_WORKSPACE echo "□ Install Flutter " time git clone -b stable $HOME/flutterĮxport PATH= " $PATH: $HOME/flutter/bin " echo "□ Flutter Precache " time flutter precache -iosĮcho "□ Install Flutter Dependencies " time flutter pub getĮcho "□ Install CocoaPods via Homebrew " time HOMEBREW_NO_AUTO_UPDATE=1 brew install cocoapodsĮcho "□ Install CocoaPods dependencies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |