CI/CD for React Native
Buddy lets you create delivery pipelines that will build, test and deploy your React Native application on a single push to a branch. The pipelines consist of actions that you can configure depending on your needs. React Native pipeline example
Configuration is very easy and takes only a couple of minutes.
1. Select your Git repository
2. Add a new delivery pipeline
Enter the pipeline's name, select the trigger mode, and define the branch from which Buddy will fetch your code: Adding a new pipeline with Buddy
Branch assignment — this is the branch from which Buddy will deploy. If you set the trigger mode to On push, Buddy will execute the pipeline upon every push to that branch.
- Manual (on click) — recommended for Production
- On push (automatic) — recommended for Development
- Recurrently (on time interval) — recommended for Staging/Testing
3. Add actions
Buddy lets you choose from dozens of predefined actions. In this example, we'll add 4 actions that will perform the following tasks:
- Build and test React Native app: download dependencies (npm, yarn, etc.), run tests, compile assets (npm tasks, webpack, etc.)
- Upload code to server together with compiled assets
- Restart application
- Send notification to Slack
3.1 Configure your React Native application
Buddy lets you configure the SDK version as well as build tools and node versions of your Android build. Configuring React Native application
3.2 Build your React Native application
Look up and click the React Native action to configure it. Here you can choose the React Native version and determine the commands to execute. The default commands are:
export ANDROID_HOME="/opt/android/sdk/" export BUILD_TOOLS_VER="28.0.3" export PATH=$PATH:/opt/android/sdk/build-tools/$BUILD_TOOLS_VER npm install cd ./android chmod +x gradlew ./gradlew assembleRelease$$$$$$$
Default React native action build commands
3.3 Sign your application (APK)
Add Sign APK action from the actions menu. Select the path of the APK and provide the keystore with its password: Configuring Sign APK
3.4 Deploy APK to Google Play
The package is now ready for deployment. Head to the Android section and select Google Play: Google Play action
When adding the action you can choose what and where should be uploaded: Configuring Google Play action
Buddy's deployment is based on changesets. This means only changed files are deployed, which makes it lightning fast ⚡️.
3.5 Send notification to Slack
You can configure Buddy to send your team a message after the deployment. In this example we'll use Slack: Notification actions
If you add this action to Actions run on failure, Buddy will only send a message if something went wrong with your build or deployment.
Congratulations! You have just automated your entire delivery process. Make a push to the selected branch and watch Buddy fetch, build, and deploy your project. With Continuous Delivery applied, you can now focus on what's really important: developing awesome apps! 🔥
Bear in mind that this article is only a brief example of what Buddy can do. You can create additional pipelines for staging and production environments, integrate with your favorite services (AWS, Google, Azure), trigger tests on pull requests, build Docker images, and push them to the registry—the possibilities are unlimited.
If you want us to create a delivery pipeline for your project, drop a line to firstname.lastname@example.org – we'll be happy to help!