You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* master:
Prepare for release 2.9.0.
Update test fixture dependencies.
SDK Command-line Tools 2.0.
Add information on running on Linux to README.md.
Fix doc.
Mention ci-matters repo in adopters list
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,9 @@
1
1
# Change Log
2
2
3
+
## v2.9.0
4
+
5
+
* Updated to SDK command-line tools `2.0`.
6
+
3
7
## v2.8.0
4
8
5
9
* Added support for specifying a custom name used for creating the **AVD** - [#59](https://github.com/ReactiveCircus/android-emulator-runner/issues/59).
A GitHub Action for installing, configuring and running hardware-accelerated Android Emulators on macOS virtual machines (or Linux virtual machines but without hardware accleration).
7
+
A GitHub Action for installing, configuring and running hardware-accelerated Android Emulators on macOS virtual machines.
8
8
9
9
The old ARM-based emulators were slow and are no longer supported by Google. The modern Intel Atom (x86 and x86_64) emulators require hardware acceleration (HAXM on Mac & Windows, QEMU on Linux) from the host to run fast. This presents a challenge on CI as to be able to run hardware accelerated emulators within a docker container, **KVM** must be supported by the host VM which isn't the case for cloud-based CI providers due to infrastructural limits. If you want to learn more about this, here's an article I wrote: [Running Android Instrumented Tests on CI](https://dev.to/ychescale9/running-android-emulators-on-ci-from-bitrise-io-to-github-actions-3j76).
10
10
@@ -24,8 +24,6 @@ This action automates the process by doing the following:
24
24
25
25
It is recommended to run this action on a **macOS** VM, e.g. `macos-latest` or `macos-10.15` to take advantage of hardware accleration support provided by **HAXM**.
26
26
27
-
Please note that while Linux VMs (e.g. `ubuntu-latest` or `ubuntu-18.04`) are also supported, hardware acceleration will **not** be available.
28
-
29
27
A workflow that uses **android-emulator-runner** to run your instrumented tests on **API 29**:
|`api-level`| Required | N/A | API level of the platform system image - e.g. 23 for Android Marshmallow, 29 for Android 10. **Minimum API level supported is 15**. |
_Please note that if you are running on a Linux VM, `-no-accel` will be added to the `emulator-options` to make sure hardware acceleration is turned off._
106
+
## Can I use this action on Linux VMs?
107
+
108
+
The short answer is yes but it's expected to be a much worse experience (on some newer API levels it might not work at all) than running it on macOS.
109
+
110
+
For a longer answer please refer to [this issue](https://github.com/ReactiveCircus/android-emulator-runner/issues/46).
111
+
111
112
112
113
## Who is using Android Emulator Runner?
113
114
@@ -126,5 +127,6 @@ These are some of the open-source projects using (or used) **Android Emulator Ru
* Installs & updates the Android SDK for the macOS platform, including SDK platform for the chosen API level, latest build tools, platform tools, Android Emulator,
25
25
* and the system image for the chosen API level, CPU arch, and target.
* Installs & updates the Android SDK for the macOS platform, including SDK platform for the chosen API level, latest build tools, platform tools, Android Emulator,
0 commit comments