New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deploy to Crashlytics Beta on merge to master #4

Open

macklinu opened this issue Jan 19, 2016 · 1 comment

Labels

chore

Milestone

Contributor

macklinu commented Jan 19, 2016

Look into automatically deploying merges to master to the Crashlytics Beta beta users list, which I believe is just @crebma and I right now.

For 1.0.0, I would manually upload builds. I'm over that.

macklinu added this to the 2.0.0 milestone

macklinu added the chore label

Contributor Author

macklinu commented May 19, 2016

I didn't upload a build along the way from 1.0.0 to 2.0.0. 😲

I'm thinking about changing the branching strategy up and will make a new issue for it. Essentially:

develop: the development branch. Pushes to this branch will deploy a debug version of the app to internal testers
master: the production branch. Pushes to this branch would build the production APK and deploy to the Google Play Store with the help of tools like Fastlane, Google Play Gradle plugins, whatever else.

macklinu modified the milestones: 3.0, 2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment