Taking /nightly-builds
to the level

Initially, building was only available to developers and had to be done through a terminal with the mobile-app repo installed, which can become inneficient.

elliot --help
[ELLIOT] Usage: elliot [OPTIONS]

Options:
    --os ios | android | all                     Set the target operating system (default: ios)
    --brand whitelabel | storybook       Set the brand name (default: inspire)
    --env available envs                      Set the environment (default: uat)
    --branch git branches                    Specify the git branch (default: current branch)
    --name name of build (optional)    Specify the name for the build (optional)
    --message message (optional)     Optional message to send in teams notification (optional)
    --dirty                                            Should use local codebase?
    --dizzy                                           Should be remote? (ignores dirty flag)
    --help                                            Display this help message

Adding --dizzy 🚜
to the Equation.

Then we added schedules, allowing us to trigger builds remotely using the Mac Mini. A .json file containing a schedule with the queue of pending builds for the Mac Mini to kick off.

Building a Complete
E2E Build Panel.

Now we are launching elliot UI, An End-to-End panel for triggering builds, detox testing, and session replays for user session crash replication.

Detox Testing

Crash Replay

Remote Builds

Build History

Build Notifs

Build Logs