Use MazeRunner environment variables where available

[twometresteve]

Goal

Make use of the new environment variables introduced in MazeRunner 3.6.0, reducing noise in the pipeline file and making it more convenient to run MazeRunner scenarios locally.

Design

The environment variables needed to drive this are stored in our S3 secrets bucket, which I have updated.

Changeset

Pipeline, Gem and Docker files. Testing guide.

Testing

I tested the updated test instructions locally by setting the variables (and now in my .bashrc!). Remainder is covered by passing CI.

[nickdowell]

Just to clarify; are these the new environment variables?

• MAZE_DEVICE_FARM_USERNAME - your BrowserStack App Automate Username
• MAZE_DEVICE_FARM_ACCESS_KEY - your BrowserStack App Automate Access Key
• MAZE_BS_LOCAL - location of the BrowserStackLocal executable on your local file system

[twometresteve]

Just to clarify; are these the new environment variables?

• MAZE_DEVICE_FARM_USERNAME - your BrowserStack App Automate Username
• MAZE_DEVICE_FARM_ACCESS_KEY - your BrowserStack App Automate Access Key
• MAZE_BS_LOCAL - location of the BrowserStackLocal executable on your local file system

Yes, they're the ones relevant to Cocoa CI. There are others you'll find useful when running the tool locally (MAZE_APPLE_TEAM_ID and MAZE_UDID). See the top section of bundle exec maze-runner --help for full details.