This repository has been archived by the owner on Feb 25, 2024. It is now read-only.
forked from bitrise-steplib/steps-avd-manager
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathstep.yml
executable file
·121 lines (113 loc) · 5.39 KB
/
step.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
title: AVD Manager
summary: |-
Create an Android emulator with the AVD Manager Step.
description: |-
Test your project in an Android emulator with the AVD Manager. Once some basic inputs are set, the Step checks the requirements, downloads and installs the packages before creating and starting the emulator.
### Configuring the Step
1. Add the **AVD Manager** Step to your Workflow as one of the first Steps in your Workflow.
2. Set the **Device Profile** to create a new Android virtual device. To see the complete list of available profiles, use the `avdmanager list device` command.
3. Set the **Android API Level**. The new virtual device will run with the specified Android version.
4. Select an **OS Tag** to have the required toolset on the new virtual device.
### Troubleshooting
The emulator needs some time to boot up. The earlier you place the Step in your Workflow, the more tasks, such as cloning or caching, you can complete in your Workflow before the emulator starts working.
We recommend that you also add **Wait for Android emulator** Step to your Workflow as it acts as a shield preventing the AVD Manager to kick in too early. Make sure you add the **Wait for Android emulator** Step BEFORE the Step with which you want to use the **AVD Manager**.
### Useful links
- [Getting started with Android apps](https://devcenter.bitrise.io/getting-started/getting-started-with-android-apps/)
- [Device testing for Android](https://devcenter.bitrise.io/testing/device-testing-for-android/)
- [About Test Reports](https://devcenter.bitrise.io/testing/test-reports/)
### Related Steps
- [Wait for Android emulator](https://www.bitrise.io/integrations/steps/wait-for-android-emulator)
- [Android Build for UI testing](https://www.bitrise.io/integrations/steps/android-build-for-ui-testing)
website: https://github.com/bitrise-steplib/steps-avd-manager
source_code_url: https://github.com/bitrise-steplib/steps-avd-manager
support_url: https://github.com/bitrise-steplib/steps-avd-manager/issues
host_os_tags:
- osx-10.10
type_tags:
- utility
is_requires_admin_user: true
is_always_run: false
is_skippable: false
toolkit:
go:
package_name: github.com/bitrise-steplib/steps-avd-manager
run_if: ""
inputs:
- profile: "pixel"
opts:
title: "Device Profile"
summary: Set the device profile to create the new AVD. This profile contains all the parameters of the devices. To see the complete list of available profiles please use the `avdmanager list device` command.
description: Set the device profile to create the new AVD. This profile contains all the parameters of the devices. To see the complete list of available profiles please use the `avdmanager list device` command.
is_required: true
- api_level: 26
opts:
title: "Android API Level"
summary: The device will run with the specified version of android.
description: The device will run with the specified version of android.
is_required: true
- tag: google_apis
opts:
title: "OS Tag"
summary: Select OS tag to have the required toolset on the device.
description: Select OS tag to have the required toolset on the device.
is_expand: true
is_required: true
value_options:
- "google_apis"
- "google_apis_playstore"
- "android-wear"
- "android-tv"
- "default"
- abi: "x86"
opts:
category: Debug
title: "ABI"
summary: Select which ABI to use running the emulator. Availability depends on API level. Please use `sdkmanager --list` command to see the available ABIs.
description: Select which ABI to use running the emulator. Availability depends on API level. Please use `sdkmanager --list` command to see the available ABIs.
is_expand: true
is_required: true
value_options:
- "x86"
- "x86_64"
- "armeabi-v7a"
- "arm64-v8a"
- "mips"
- emulator_id: "emulator"
opts:
category: Debug
title: "ID"
summary: Set the device's ID. (This will be the name under $HOME/.android/avd/)
description: Set the device's ID. (This will be the name under $HOME/.android/avd/)
is_required: true
- create_command_flags: "--sdcard 512M"
opts:
category: Debug
title: "Create AVD command flags"
summary: Flags used when running the command to create the emulator.
description: Flags used when running the command to create the emulator.
is_required: false
- start_command_flags: "-camera-back none -camera-front none -no-window"
opts:
category: Debug
title: "Start AVD command flags"
summary: Flags used when running the command to start the emulator.
description: Flags used when running the command to start the emulator.
is_required: false
- emulator_channel: "0"
opts:
category: Debug
title: "Emulator channel"
summary: Select which channel to use with `sdkmanager` to fetch `emulator` package. Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).
description: Select which channel to use with `sdkmanager` to fetch `emulator` package. Available channels are 0 (Stable), 1 (Beta), 2 (Dev), and 3 (Canary).
is_expand: true
is_required: true
value_options:
- "0"
- "1"
- "2"
- "3"
outputs:
- BITRISE_EMULATOR_SERIAL:
opts:
title: "Emulator serial"
description: "Booted emulator serial"