Update chromium-render to use Debian Chromium

Authored by Niedzielski on Feb 8 2018, 6:51 PM.


Update chromium-render to use Debian Chromium

Update chromium-render-npm-browser-node-6-docker to use the Debian
system Chromium installation provided by Docker. This requires that
chromium-render's Puppeteer dependency be configured to skip downloading
Chromium when an npm install is performed:

  • PUPPETEER_SKIP_CHROMIUM_DOWNLOAD is set or NPM configured with puppeteer_skip_chromium_download enabled. The former was chosen since a change in production and development installation behavior is undesirable (see comments in change) and the ability to test both states easily in Jenkins may be useful.
  • The RESTBase service configuration is configured to point to the system Chromium executable. Unfortunately, there is no environment variable or other seam. Two options were considered: 1) a new YAML config that CI could update the config symlink to point to; 2) edit the existing config in CI. The former option was not chosen because there seems to be no way to selectively override a Swagger config and maintaining a duplicate configuration with a single change is error prone.

Finally, this patch also promotes the existing experimental job to
test and gate-and-submit.

This configuration was verified by using Jenkins "rebuild last" button
which properly supplies the new PUPPETEER_SKIP_CHROMIUM_DOWNLOAD build
parameter as an environment variable. Builds triggered from Gerrit still
seem to require check experimental pipeline instead of recheck and
are not using the environment variable.

Bug: T179552
Bug: T186748
Change-Id: Ib32f3e8a212d72f32b542ffaccc4b9da629f5d0d


NiedzielskiFeb 13 2018, 4:56 PM
rCICF7dc20f0cd1fe: Make debian-glue voting on debian-glue repo