Overview

Currently, we re-run the installation and webpack build steps in each of our E2E tests. This results in redundant builds. We should instead re-architect the CI jobs to be something like this:

                       +--Run a set of E2E tests
                       |
Install and Build -----+--Run a set of E2E tests
                       |
                       +--Run a set of E2E tests

where jobs on the left run first, and lines connect dependent builds.

Implementation

Roughly, here's the implementation approach I'm envisioning:

• Install and Build
  • Install dependencies
  • Build webpack
  • Save/upload the dependencies and built webpack files
• Run E2E tests
  • Load/download the dependencies and built webpack files
  • Run the E2E tests