GitHub provides basic documentation on how actions/workflows work and how to create them.
Create new workflow using visual editor or manually in file
Define build steps (aka Actions) of the workflow and dependencies between them (see Creating a new GitHub Action).
For this Android project, special actions were created:
See these projects'
Dockerfilefiles for configuration details.
email@example.com regular build steps and provide commands via action
argsparameter. For example:
args = "./gradlew assembleDebug -PpreDexEnable=false". This will be passed to
entrypoint.shof the appropriate GitHub Action and executed in root folder of the workspace.
To modify the way Android UI tests are executed, you need to override
/usr/bin/run-ui-testsscript and provide custom way of executing UI tests. Alternatively, use another GitHub Action or Docker image. By default, UI tests will be executed via
See .github/man.workflow with final configuration.
FABRIC_API_TOKENsecrets via Actions UI editor
Once secrets are created via editor, they will be automatically used in Action from which you initiated the secrets creation. For any other Action which needs secrets or environment variables we need to either specify them
via visual editor
or directly in workflow file as follows
secrets = ["FABRIC_API_KEY", "FABRIC_API_SECRET"]
Project will be built on every
pushaction (both from branches and PR's)