Run your tests using Flank. The step will automaticall detect which project type your flank config uses and the corresponding flank command will be ran.
- google_service_account_json: (required) (sensitive)
Service Account JSON key file content.
- config_path: (required)
Flank config file path.
- version: latest (required)
Flank binary version. You can use any tag name that is available on https://github.com/Flank/flank/releases or latest which will download the latest non-pre-release version.
- command_flags:
These flags will be appended to the flank command.
- ./results/{latest-result-dir}/: $BITRISE_DEPLOY_DIR/
- Fork this repository
- Make changes
- Submit a PR
- Clone this repository
cd
to the cloned repository's root- Create a bitrise.yml (if not yet created)
- Prepare a workflow that contains a step with the id:
path::./
For example:
format_version: "6" default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git workflows: my-workflow: steps: - path::./: inputs: - google_service_account_json: $GOOGLE_SERVICE_ACCOUNT - config_path: ./flank.yml
- Run the workflow:
bitrise run my-workflow
This is an official Step managed by Bitrise.io and is available in the Workflow Editor and in our Bitrise CLI tool. If you seen something in this readme that never before please visit some of our knowledge base to read more about that:
- devcenter.bitrise.io
- discuss.bitrise.io
- blog.bitrise.io