Change Details

The service-runner `build` functionality uses a jessie docker image to compile dependencies for deploy repositories. Now that production is switching to a Node 4.2 backport we should switch to a jessie image that is using the precise packages we are using in production. The simplest approach should be to layer on top of the regular jessie image, by - configuring the Wikimedia repository, and - running apt-get update & upgrade, followed by an installation of nodejs.

The service-runner `build` functionality uses a jessie docker image to compile dependencies for deploy repositories. Now that production is switching to a Node 4.2 backport we should switch to a jessie image that is using the precise packages we are using in production. The simplest approach should be to layer on top of the regular jessie image, by - configuring the Wikimedia repository, and - running apt-get update & upgrade, followed by an installation of nodejs. Alternatively, we could build a complete image from scratch using the wikimedia mirror of jessie. Given the large overlap with production I'm not sure that it would be worth the effort. @moritzmuehlenhoff, @fgiunchedi, @faidon, @mobrovac, @eevans, @pchelolo: Any thoughts on this?

The service-runner `build` functionality uses a jessie docker image to compile dependencies for deploy repositories. Now that production is switching to a Node 4.2 backport we should switch to a jessie image that is using the precise packages we are using in production. The simplest approach should be to layer on top of the regular jessie image, by - configuring the Wikimedia repository, and - running apt-get update & upgrade, followed by an installation of nodejs. Alternatively, we could build a complete image from scratch using the wikimedia mirror of jessie. Given the large overlap with production I'm not sure that it would be worth the effort. @moritzmuehlenhoff, @fgiunchedi, @faidon, @mobrovac, @eevans, @pchelolo: Any thoughts on this?