The parsoid and parsoid/deploy repositories are still running jobs using NodeJS 0.8 and 0.10 on CI slaves which are permanent and respectively Precise and Trusty.
I would like to have all the jobs migrated to disposable instances provided by #nodepool. They come with Debian Jessie and we have NodeJS 4.3.
Is Parsoid fine with dropping CI for npm 0.8/0.10 ? What do you think about having CI to run on NodeJs 4.3 given rest of services is transitioning there.
For reference the complete CI workflow for both repository is as of Feb 15th 2016:
```
lang=yaml
- name: mediawiki/services/parsoid
check:
- parsoidsvc-jslint
test:
- parsoidsvc-jslint
- parsoidsvc-php-parsertests
- parsoidsvc-source-parse-tool-check
- parsoidsvc-source-roundtrip-test-check
- parsoidsvc-source-npm-0.8
- parsoidsvc-source-npm-0.10
gate-and-submit:
- parsoidsvc-jslint
- parsoidsvc-php-parsertests
- parsoidsvc-source-parse-tool-check
- parsoidsvc-source-roundtrip-test-check
- parsoidsvc-source-npm-0.8
- parsoidsvc-source-npm-0.10
postmerge:
- beta-parsoid-update-eqiad
- parsoidsvc-source-jsduck-publish
```
```
lang=yaml
- name: mediawiki/services/parsoid/deploy
check:
- parsoidsvc-jslint
test:
- parsoidsvc-jslint
- parsoidsvc-debian-glue
- parsoidsvc-deploy-parse-tool-check
- parsoidsvc-deploy-roundtrip-test-check
- parsoidsvc-deploy-npm-0.8
- parsoidsvc-deploy-npm-0.10
gate-and-submit:
- parsoidsvc-jslint
- parsoidsvc-deploy-parse-tool-check
- parsoidsvc-deploy-roundtrip-test-check
- parsoidsvc-deploy-npm-0.8
- parsoidsvc-deploy-npm-0.10
postmerge:
- beta-parsoid-update-eqiad
```