FASTLANE XCODE CLOUD ARCHIVE
This environment variable is set by Xcode Cloud automatically on every build with an archive step.
FASTLANE XCODE CLOUD INSTALL
To install Fastlane using ruby's Bundler, you need to create a Gemfile at the root of the repository and add Fastlane as a dependency:įastfile lane :upload_to_appcenter do # 1 archive_path_dir = ENV # 2 pkg_file = File. I have personally also found this way to be faster and more reliable. The easiest way to install Fastlane is using Homebrew, but the way Fastlane recommends installing it is by using ruby's Bundler. If you want to learn more about this, you can check out my blog post on the topic. As it stands, there is no way to add a custom post-action to the workflow from Xcode's user interface.ĭespite this, Xcode Cloud provides a way of running custom actions at three different stages of a workflow's lifecycle (after the repository is cloned and before and after the xcodebuild command runs) by creating scripts with specific names in a directory called ci_scripts. So far, the workflow only archives the application and distributes the generated artefact to TestFlight. In the post-action configuration, select the archive from the previous step as the artefact and a distribution group of internal beta testers to upload the build to. To achieve this, click on the + button next to the Post-Actions section title and select TestFlight Internal Testing from the list. The final step of the workflow is to upload the build to TestFlight. In the action's settings, select the scheme you want to archive the app for and set the Deployment Preparation to Internal Testing Only: Click on the + button next to the Actions section title on the left-hand side and select the Archive action from the list. Now that you have set up the environment, you need to add an action to the workflow. This ensures that you only keep the builds you are interested in and don't waste resources on builds that are no longer relevant. I suggest you select the Auto-cancels Builds option to ensure that any ongoing builds of this workflow are cancelled when a new commit is pushed to the main branch. This workflow archives and distributes the application on every push to the main branch, but you can change this to run on PR changes, on tag pushes or even on a schedule. The next step is to set up the start conditions for the workflow. Tick the secret box to ensure Xcode Cloud stores the variable securely and does not display it in the logs. Once you have generated this from AppCenter's dashboard, make sure you add it to the Environment Variables section of the workflow so you can retrieve it later on. To upload to AppCenter, you will need an API key.
Pick a macOS and an Xcode version for this workflow and tick the Clean box if you want the workflow to ignore the derived data and caches from previous jobs. Next, select the Environment tab on the left-hand side. Modify the name and description and select Restrict editing if you want the workflow to only be editable by users with Admin or App Manager roles in App Store Connect: You will now be prompted with a modal containing general information on the workflow. On the cloud tab, select your Xcode Cloud product, click on Manage Workflows and press the + button on the bottom left of the Manage Workflows screen. To do this, open Xcode and show the report navigator in the sidebar. The first step is to create a new workflow in Xcode Cloud. For this reason, I was keen to find a way to upload builds to an external service using Xcode Cloud by making use of existing Fastlane logic. I work at a company where we use AppCenter to distribute all our internal builds to other developers, testers and stakeholders.
FASTLANE XCODE CLOUD HOW TO
One of the workflows that I will be showing how to build during my talk deploys beta versions of an iOS app for internal testing and distributes them both to TestFlight and Microsoft's AppCenter. This has helped me prepare for my talk and look at Xcode Cloud in depth. In preparation for my talk at NYSwifty next week, I have been writing about all things Xcode Cloud on my blog. Release management by mobile engineers, for mobile engineers.
0 kommentar(er)
