learningequality / learningequality/studio
QA Ready Label: Would be awesome to have again
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Desired behavior
A while back. @lyw07 created a system that deployed a demo server of Studio for a PR when the label QA Ready was added to the PR. It was very convenient - a PR submitter could pop that label on there and anybody who showed up could jump into a running Studio with the PR's changes.
Current behavior
It doesn't work.
Value add
- Studio takes a while to spin up from zero so it'd save reviewers the need to open a terminal and spin up Studio to test small changes.
- Testing Studio, a public web application, in a Production-like environment could help avoid bugs that can easily be missed locally.
Possible tradeoffs
This didn't seem like easy work then and I'm sure it wouldn't be now. Additionally, we'd need to consider the costs of spinning up GCP servers and I'm not sure what database was used in the original implementation.
Add labels
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the earlier QA Ready implementation created by @lyw07 and the current PR-label deployment workflow to determine why it no longer works. Identify the GCP and database setup needed for a PR-specific Studio server; done means adding the label reliably produces a usable demo environment for reviewers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- ci-cd, cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100