Docs
HomeAboutBlogGithub
Search…
What is Simple?
Try it out
Training materials
What we report
Building custom reports
Customer support
Code of conduct
Digital principles
Contact us
Engineering
Environments
Data dictionary & API
Tooling & infrastructure
Release notes
Android
Conventions
Deploying to Play Store
Bitrise Workflow Quirks
Headers sent from the app
Backend
Localization
Design
Design
User testing
Onboarding
Acronyms
Glossary
Recommended reading
Elsewhere
Simple.org
Source code (GitHub)
Join our Slack (Slack)
Powered By GitBook
Bitrise Workflow Quirks
We currently have four workflows which generate builds:
    build-demo-sand-prod-apks: This workflow builds the APKs for all environments (SANDBOX, DEMO, PRODUCTION) and makes them available for download.
    deploy-sandbox-to-play-store: This workflow builds the SANDBOX APK and deploys it to the Play Store.
    deploy-demo-to-play-store: This workflow builds the DEMO APK and deploys it to the Play Store.
    deploy-prod-to-play-store: This workflow builds the PRODUCTION APK and deploys it to the Play Store.
The quirk here to note is that the gradle build command is duplicated across all of these builds. The gradle config for build-demo-sand-prod-apks is hardcoded as part of the workflow, whereas for the others, there are sub-workflows named _gradle-sandbox-build, _gradle-sandbox-build, and _gradle-prod-build respectively.
Currently, if you need to make a change to the gradle build command, you need to make the change in ALL of these workflows.
Previous
Deploying to Play Store
Next
Headers sent from the app
Last modified 2yr ago
Export as PDF
Copy link