Start Genymotion Cloud SaaS Android devices
Go to Genymotion Cloud SaaS and create an account
Can be run directly with the bitrise CLI,
just git clone
this repository, cd
into it's folder in your Terminal/Command Line
and call bitrise run test
.
Check the bitrise.yml
file for required inputs which have to be
added to your .bitrise.secrets.yml
file!
Step by step:
- Open up your Terminal / Command Line
git clone
the repositorycd
into the directory of the step (the one you justgit clone
d)- Create a
.bitrise.secrets.yml
file in the same directory ofbitrise.yml
(the.bitrise.secrets.yml
is a git ignored file, you can store your secrets in it) - Check the
bitrise.yml
file for any secret you should set in.bitrise.secrets.yml
- Best practice is to mark these options with something like
# define these in your .bitrise.secrets.yml
, in theapp:envs
section.
- Once you have all the required secret parameters in your
.bitrise.secrets.yml
you can just run this step with the bitrise CLI:bitrise run test
An example .bitrise.secrets.yml
file:
envs:
- GMCLOUD_SAAS_EMAIL: [YOUR_GENYMOTION_CLOUD_EMAIL]
- GMCLOUD_SAAS_PASSWORD: [YOUR_GENYMOTION_CLOUD_PASSWORD]
This step takes three inputs:
recipe_uuid
: Recipe UUID is the identifier used when starting an instance; it can be retrieved usinggmsaas recipes list
adb_serial_port
(default value: None): port which the instance will be connected to ADB
Example:
- Start single instance:
inputs:
- email: $GMCLOUD_SAAS_EMAIL
- password: $GMCLOUD_SAAS_PASSWORD
- recipe_uuid: e20da1a3-313c-434a-9d43-7268b12fee08
- adb_serial_port: 4321
- Start several instances:
inputs:
- email: $GMCLOUD_SAAS_EMAIL
- password: $GMCLOUD_SAAS_PASSWORD
- recipe_uuid: e20da1a3-313c-434a-9d43-7268b12fee08,c52fdfc2-6914-4266-aa6e-50258f50ef91,06867de4-4b99-4842-ba40-fd3daaabdf23
- adb_serial_port: 4321,4324,4325
This step is part of a series of Bitrise steps which integrate Genymotion Cloud SaaS with Bitrise.
- Use the Stop Genymotion Cloud SaaS android devices step to stop your Android devices to Genymotion Cloud SaaS.
- Fork this repository
git clone
it- Create a branch you'll work on
- To use/test the step just follow the How to use this Step section
- Do the changes you want to
- Run/test the step before sending your contribution
- You can also test the step in your
bitrise
project, either on your Mac or on bitrise.io - You just have to replace the step ID in your project's
bitrise.yml
with either a relative path, or with a git URL format - (relative) path format: instead of
- original-step-id:
use- path::./relative/path/of/script/on/your/Mac:
- direct git URL format: instead of
- original-step-id:
use- git::https://github.com/user/step.git@branch:
- You can find more example of alternative step referencing at: https://github.com/bitrise-io/bitrise/blob/master/_examples/tutorials/steps-and-workflows/bitrise.yml
- Once you're done just commit your changes & create a Pull Request