Change Details

The CI job `wikimedia-portals-build` should be migrated to use Docker container. See also {T210286}, the job is similar but the solution will certainly be different.

The CI job `wikimedia-portals-build` should be migrated to use Docker container. As of July 2019 it runs on Jenkins instances based on Debian Jessie which are provisioned with puppet. That infrastructure is deprecated and has to be dismissed in favor of using Docker containers. The job `wikimedia-portals-build` runs every Monday and roughly: * git clone `wikimedia/portals.git` * run `npm install` && `npm test` && `npm run-script build-all-portals`, that results in assets intended to power https://www.wikipedia.org/ * Craft a commit adding the content of `./prod` and send that to Gerrit for review against `wikimedia/portals/deploy.git` * A human +2 the change, once merged `operations/mediawiki-config.git` has the submodule bumped and the portal assets are deployed using a wrapper around scap, similar to how mediawiki-config changes are deployed. ---- We should be able to use the #release_pipeline to orchestrate the CI build and ultimately switch https://www.wikipedia.org/ to be served by kubernetes. See also {T210286}, the job is similar but the solution will certainly be different.

The CI job `wikimedia-portals-build` should be migrated to use Docker container. As of July 2019 it runs on Jenkins instances based on Debian Jessie which are provisioned with puppet. That infrastructure is deprecated and has to be dismissed in favor of using Docker containers. The job `wikimedia-portals-build` runs every Monday and roughly: * git clone `wikimedia/portals.git` * run `npm install` && `npm test` && `npm run-script build-all-portals`, that results in assets intended to power https://www.wikipedia.org/ * Craft a commit adding the content of `./prod` and send that to Gerrit for review against `wikimedia/portals/deploy.git` * A human +2 the change, once merged `operations/mediawiki-config.git` has the submodule bumped and the portal assets are deployed using a wrapper around scap, similar to how mediawiki-config changes are deployed. ---- We should be able to use the #release_pipeline to orchestrate the CI build and ultimately switch https://www.wikipedia.org/ to be served by kubernetes. See also {T210286}, the job is similar but the solution will certainly be different.