Skip to content
This repository has been archived by the owner on Apr 13, 2020. It is now read-only.

Continuous deployment #237

Open
ismail-s opened this issue Feb 27, 2017 · 0 comments
Open

Continuous deployment #237

ismail-s opened this issue Feb 27, 2017 · 0 comments

Comments

@ismail-s
Copy link
Owner

This issue needs some thought about whether or not it should be done, and if so, to what extent/in what way.

Background

At the moment, JTime gets big deployments which I plan to keep doing as I have found people don't like getting lots of updates to Android apps (or more specifically, get annoyed at the constant notifications about updates). However, with the last 2 deployments, I have encountered unexpected issues when the automated deployment occurred, necessitating me to manually deploy or fix the automated deployment. Continuously deploying to a staging environment could help spot these issues earlier.

Questions to be resolved

  • Out of JTime-rest, JTime-website and JTime-android, which should have a staging environment thing?
  • How should db schema modifications be handled?
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant