Skip to content

Different yarn versions on different build images is causing failures

Currently we have different versions of yarn contained in different build images:

# in ruby-2.3.3-golang-1.8-git-2.13-phantomjs-2.1-node-7.1-postgresql-9.6

$ yarn --version
0.27.5

# in ruby-2.3.3-golang-1.8-git-2.13-chrome-59.0-node-7.1-postgresql-9.6

$ yarn --version
0.24.6

The latter image is used in the rake karma job, and this job is failing in some circumstances because yarn check from v0.24.6 can fail unexpectedly when run against node_modules populated by yarn install on v0.27.5.

We need to either:

  1. ensure all build images pass CI when generated in tandem, and not ignore those that don't because doing so can have unforeseen consequences. this likely happened because the chrome build image has failed on a few recent CI runs and was ignored

  2. lock down the yarn install version (if possible) to ensure consistency across build images