WhoBuilt

Continuous Integration With Microsoft App Center

Oct 8, 2019· 11 min· 3.3K views·Watch on YouTube

Speaker

Nick de Jesus, a React Native developer and professional esports player, explains how he uses Microsoft App Center to build, test, and distribute his Tekken companion app, T7 Chicken, at React Native EU 2019 with Callstack.

Why automate deployments

De Jesus describes manual React Native deployments as tedious and says he was too lazy to set up Fastlane. He notes that Fastlane can automate processes such as code signing and works with different CI tools; App Center uses it under the hood.

Distribute builds and update JavaScript

App Center distribution groups let him upload an IPA or APK with notes so invited testers can download a build before a formal store release. For later releases, he shows TestFlight groups and release history. CodePush can deliver fixes to the JavaScript parts of a React Native app, with controls for mandatory updates and active-device counts.

Configure branch builds and signing

App Center connects to a GitHub repository and offers per-branch build settings, including scripts, build triggers, unit tests, and linting. De Jesus highlights automatic version incrementing and the choice of Android App Bundle or APK. Signing setup involves uploading a keystore and entering its password.

Test on devices and send builds out

The service can run builds on virtual iOS and Android devices and provide data for each run; de Jesus mentions a 30-day free trial. Builds can go to App Center tester groups through a shareable URL or to store channels such as Android alpha, beta, and production.

Resilient Coders

De Jesus works at Resilient Coders, a Boston nonprofit focused on closing the opportunity gap for underrepresented people of color in tech. Its 14-week boot camp pays participants to learn coding and prepares them for full-stack engineering work. He gives an augmented reality tattoo web app by a recent graduate as an example project.

Takeaways

  • Use App Center distribution groups for quick tester feedback before submitting through app stores.
  • CodePush can ship JavaScript fixes while a fuller app release is being prepared.
  • Automated version increments can prevent forgotten version updates in build workflows.
  • Set branch build triggers deliberately; building on every push can become excessive.
  • Keep signing credentials within the build service instead of passing keystore files informally.

Mentioned in this talk

Search inside this talk

What was claimed 13

Show all 13 facts

Related talks