Tuesday the 12th May is two weeks after announcing deprecation of the
install-* roles [1] and the date we should starting throwing an error
message to direct the user to use the renamed ensure-* role instead.
[1]
http://lists.zuul-ci.org/pipermail/zuul-announce/2020-April/000071.html
Change-Id: Ie2474c5c0704aa44f51bdd5d7afddb8c7e4e578b
I can't exactly say why, but the horizon postinstall in package.json
runs "tox -e npm" [1]. This then installs from requirements [2].
The requirements gate run a cross-horizon-npm job that ends up calling
this. The short story is that if you modify upper-constraints.txt in
a requirements change, it is not picked up by this job.
Add tox_constraints_file to this job, so we can set the path to the
zuul checked-out version for the test.
[1] e515713084/package.json (L22)
[2] e515713084/tox.ini (L23)
Needed-By: https://review.opendev.org/709389
Change-Id: Ia7dd5af19b42c2ab53dfb70f92e184b0dc215d03
Some javascript projects use yarn for dependencies instead of raw npm.
If a yarn.lock file is detected in the zuul_work_dir, install yarn and
use yarn to install dependencies.
Needed-By: I5864e1b2f9952fbc35b08ebdef348c4917564c37
Change-Id: I9ae7dd3b33b2b607c1c5a17632e2aeb12e339d15