Datasets:
Ekhlass
/
flutter_docs

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
1
372
<topic_end>
<topic_start>
continuous delivery with flutter
follow continuous delivery best practices with flutter to make sure your
application is delivered to your beta testers and validated on a frequent basis
without resorting to manual workflows.
<topic_end>
<topic_start>
CI/CD options
there are a number of continuous integration (ci) and continuous delivery (cd)
options available to help automate the delivery of your application.
<topic_end>
<topic_start>
all-in-one options with built-in flutter functionality
<topic_end>
<topic_start>
integrating fastlane with existing workflows
you can use fastlane with the following tooling:
this guide shows how to set up fastlane and then integrate it with
your existing testing and continuous integration (ci) workflows.
for more information, see “integrating fastlane with existing workflow”.
<topic_end>
<topic_start>
fastlane
fastlane is an open-source tool suite to automate releases and deployments
for your app.
<topic_end>
<topic_start>
local setup
it’s recommended that you test the build and deployment process locally before
migrating to a cloud-based system. you could also choose to perform continuous
delivery from a local machine.
on iOS, follow the
fastlane iOS beta deployment guide.
you can specify the archive path to avoid rebuilding the project. for example:
you’re now ready to perform deployments locally or migrate the deployment
process to a continuous integration (ci) system.
<topic_end>
<topic_start>
running deployment locally
<topic_end>
<topic_start>
cloud build and deploy setup
first, follow the local setup section described in ‘local setup’ to make sure
the process works before migrating onto a cloud system like travis.
the main thing to consider is that since cloud instances are ephemeral and
untrusted, you won’t be leaving your credentials like your play store service
account JSON or your iTunes distribution certificate on the server.
continuous integration (ci) systems generally support encrypted environment
variables to store private data. you can pass these environment variables
using --dart-define MY_VAR=MY_VALUE while building the app.
take precaution not to re-echo those variable values back onto the console in
your test scripts. those variables are also not available in pull requests
until they’re merged to ensure that malicious actors cannot create a pull
request that prints these secrets out. be careful with interactions with these
secrets in pull requests that you accept and merge.
<topic_end>
<topic_start>
xcode cloud
xcode cloud is a continuous integration and delivery service for building,
testing, and distributing apps and frameworks for apple platforms.
<topic_end>
<topic_start>
requirements
<topic_end>
<topic_start>
custom build script
xcode cloud recognizes custom build scripts that can be
used to perform additional tasks at a designated time. it also includes a set
of predefined environment variables, such as $ci_workspace, which is the
location of your cloned repository.
info note
the temporary build environment that xcode cloud uses includes tools that are
part of macOS and xcode—for example, python—and additionally homebrew to
support installing third-party dependencies and tools.
<topic_end>
<topic_start>
post-clone script
leverage the post-clone custom build script that runs after
xcode cloud clones your git repository using the following instructions:
create a file at ios/ci_scripts/ci_post_clone.sh and add the content below.
<code_start>
#!/bin/sh
# fail this script if any subcommand fails.
set -e
# the default execution directory of this script is the ci_scripts directory.
cd $ci_primary_repository_path # change working directory to the root of your cloned repo.
# install flutter using git.
git clone https://github.com/flutter/flutter.git --depth 1 -b stable $home/flutter
export PATH="$PATH:$HOME/flutter/bin"
# install flutter artifacts for iOS (--ios), or macOS (--macos) platforms.
flutter precache --ios
# install flutter dependencies.
flutter pub get
# install CocoaPods using homebrew.
HOMEBREW_NO_AUTO_UPDATE=1 # disable homebrew's automatic updates.
brew install cocoapods
# install CocoaPods dependencies.
cd ios && pod install # run `pod install` in the `ios` directory.
exit 0