Skip to content
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

Investigate & document steps to perform complete Oppia Android development in a VM #3437

Closed
BenHenning opened this issue Jul 7, 2021 · 2 comments
Closed

Investigate & document steps to perform complete Oppia Android development in a VM #3437

BenHenning opened this issue Jul 7, 2021 · 2 comments
Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@BenHenning
Copy link
Member

Per #3371 Bazel development support is very limited on Windows. While we know a subsystem is a viable path forward for Bazel, it introduces an awkward bifurcation where the repository lives in Windows & the user does development via Windows Android Studio, but uses Bazel within an Ubuntu subsystem.

A better alternative might be to instead set up a VM and run both Android Studio and Bazel from the same Unix-based environment. We need to investigate & document the steps to ensure this approach is viable for all aspects of Oppia Android development:

  • Using git to clone & modify Oppia Android
  • Running Android Studio
  • Building & running tests via Gradle (in Android Studio)
  • Building & running tests via Bazel (CLI)
  • Deploying the app binary & tests to a real device
  • Starting an emulator
  • Deploying the app binary & tests to an emulator
@BenHenning BenHenning added this to the Beta MR2 milestone Jun 11, 2022
@Broppia Broppia added issue_type_infrastructure Impact: Low Low perceived user impact (e.g. edge cases). labels Jul 14, 2022
@BenHenning BenHenning added Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Z-ibt Temporary label for Ben to keep track of issues he's triaged. and removed Impact: Low Low perceived user impact (e.g. edge cases). labels Sep 16, 2022
@BenHenning BenHenning removed this from the Beta MR2 milestone Sep 16, 2022
@seanlip seanlip added enhancement End user-perceivable enhancements. and removed issue_type_infrastructure labels Mar 28, 2023
@MohitGupta121 MohitGupta121 added the Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. label Jun 16, 2023
@MohitGupta121
Copy link
Member

MohitGupta121 commented Jun 16, 2023 •
edited
Loading

@BenHenning we can say this particular issue is also part of this issue #2746 becuase we are now giving proper doc of Bazel for all OS ?

@seanlip seanlip mentioned this issue Jun 16, 2023
Open
@seanlip
Copy link
Member

seanlip commented Jun 16, 2023

I think that's fine and I've modified #2746 accordingly. Closing this one.

@seanlip seanlip closed this as not planned Won't fix, can't repro, duplicate, stale Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement End user-perceivable enhancements. Impact: Medium Moderate perceived user impact (non-blocking bugs and general improvements). Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Projects
[Team] Developer Workflow & Infrastructure - Android
Archived in project
Milestone
No milestone
Development

No branches or pull requests
4 participants
@seanlip @BenHenning @MohitGupta121 @Broppia