Skip to main content

Bitrise CI template for a React native app

Here is a conceptual monopipeline for building and deploying a React native app to the app stores in Bitrise. The described pipeline serves us well, and I discuss the benefits and tradeoffs in the afterword.


Setting up .env and release method

The first step is for the CI machinery to overwrite or add relevant environment variables based on the branch/tag. You can already at this point determine if this pipeline will release the app to the stores or just run through the build.

Run linters and tests, check test coverage

For TS/JS, these can be just npm scripts in the Bitrise npm step. For native code, you can use the predefined steps or run some Gradle tasks. Prefer one-liners: avoid writing complicated initialization commands. npm run lint, npm run test:coverage...

Set release versions

You could simply use the git tag here for the version. You could also use automatic semver and tools such as commitizen to version the build. For private builds, X.Y.BUILD_NUMBER is enough. There is a Bitrise step for both iOS and Android.

Run iOS build

Run and create an archive, use the export method determined by the first step(s).

Conditional step, deploy to the app store.

The previous CI steps should result in a flag (ENV) to determine if we should deploy or not, and should we deploy all the way to production or just to Testflight.

Download Android upload signing keystore. 

The keystore should be stored in some secure location. You can use the Bitrise predefined step for this and upload the keystore to Bitrise.

Build Android

Similar to the iOS step

Conditional step, deploy to Play store

Yes, we can end up in a situation where the iOS app is in the app store, and the Android app does not build and does not end up in the store. In case of fire, do manual steps :/

Run codecov / deepcode.ai / whatever

Some extra static analysis for your code

Upload and trigger Device farm tests

Can be done for both platforms or only one. Since the tests can take a while, this step is not blocking. Use some other tool to check the test results from the Device farm. If you release from this CI pipeline to production, this pipeline setup does not work since you would need to cancel the release if this step fails.

Send a slack message.

It can contain the release version, test/static analysis result links, and a download URL. You could send it only if the build fails to avoid spam.


The benefit of having only one pipeline is simplicity; we can see what is happening at one glance. We don't need to move artifacts around, and we guarantee that the configs and versions are the same for both apps. The downside is that in situations where we want to treat them separately, for example, release a fix for only for Android, we need to do some tricks to run only the iOS part of the pipeline.  Automating the release to production with screenshots and release notes would also require some shuffling of the steps. You would, in that case, want to run the device tests before the store upload.

Labels:

Comments

Post a Comment

Popular posts from this blog

Bird is causing high CPU on my macOS

There is no lack of people complaining about MacOS Tahoe, mostly about rounded corners and inconsistent design decisions. I have not paid that much attentention to that, but there is one mac bug i have paid attention to. It hasn't been a visual or ux but rather few system processes pegging the CPU. trustd , alongside with ecosystemd and ecosystemanalyticsd all reported high CPU usage. I can't exactly recall when this started, it might have predated my Tahoe upgrade but anyway, the trio of processes all had high CPU usage. Sure, it may have been the virtual efficiency cores and whether it affeced battery life or slowed down other processes i don't know to be hon...
Post a Comment
Read more

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...
Post a Comment
Read more

How my work has changed in the past few years

When I started at my current job 3ish years ago, we had nothing but a few PowerPoint slides and a Figma prototype. I recall talking with one of the founders, whom I had worked with some 10 years ago, and pointing out that the very next step after PowerPoint and Figma was still the same as it had always been: translating those slides and mockups into CRUDs, forms, and other basic building blocks. Sure, all the new fancy tools and frameworks (we had jQuery then) help, but I still had to tinker with very basic primitives like tables and forms. I could not just say, "here is a table, here is a form." Well, yes, technically I could, but I still needed to write a lot of code to make a working form or table. This was around the time of GPT-3, Copilot beta, and very early Cursor. I did attempt to use them, but they could only perform very basic tasks and were pretty much useless for frontend work. We, being one of the first-wave "ChatGPT wrapper" startups has naturally pus...
Post a Comment
Read more