2 ms·
You just described the situation mobile app developers face every day. 1/ Have slower thoughtful release cycles 2/ Construct a test release plan and hire a QA
by itake 4y ago
You just described the situation mobile app developers face every day.
1/ Have slower thoughtful release cycles
2/ Construct a test release plan and hire a QA to perform the test every release.
3/ Feature flag releases (have the device check an api to see what is actually allowed to be enabled)
> True CI/CD is out of the question since we have no way to automatically release.
CircleCI thinks you can[0]? Google has apis for everything.
[0] - https://circleci.com/blog/continuously-deploy-a-chrome-extension/ https://circleci.com/blog/continuously-deploy-a-chrome-exten...
- StriverGuy 4y agoThis is somewhat helpful, however it doesn't get past the main concern of rollbacks/deploy approvals. We already use CI to build and prep the versions each time we go out to production, but if we miss anything in QA we are up a creek without a paddle.
- jerdog 4y agoWith the link that @itake posted above, you can definitely use CircleCI to do the deploy automatically. Now if you're concerned about missing something in QA, you could add an approval step (https://circleci.com/docs/workflows#holding-a-workflow-for-a-manual-approval https://circleci.com/docs/workflows#holding-a-workflow-for-a...) in your CircleCI pipeline so that the browser extension is deployed locally for testing, and once it's been tested you can have the next steps approved where it deploys to Production (Google). This concern is really the same for anyone, regardless of if you use CircleCI or not. DISCLAIMER: I work for CircleCI