Page MenuHomePhabricator

Remove jshint from V+1 as well as V+2 pipes for repos that use eslint now
Closed, ResolvedPublic

Description

At least WikiEditor, probably quite a few others. When we switched we removed all the jshint over-rides, so those will fail.

Event Timeline

If we do this. Non whitelisted users will not have any js test run.

If we do this. Non whitelisted users will not have any js test run.

Indeed.

Change 349883 had a related patch set uploaded (by Hashar):
[integration/config@master] [Score] remove jshint, has been moved to eslint

https://gerrit.wikimedia.org/r/349883

Change 349884 had a related patch set uploaded (by Hashar):
[integration/config@master] [TemplateSandbox] remove jshint, has been moved to eslint

https://gerrit.wikimedia.org/r/349884

Change 349883 merged by jenkins-bot:
[integration/config@master] [Score] remove jshint, has been moved to eslint

https://gerrit.wikimedia.org/r/349883

Change 349884 merged by jenkins-bot:
[integration/config@master] [TemplateSandbox] remove jshint, has been moved to eslint

https://gerrit.wikimedia.org/r/349884

Change 349439 had a related patch set uploaded (by Hashar):
[integration/config@master] Clean out jsonlint/jshint

https://gerrit.wikimedia.org/r/349439

Change 349439 merged by jenkins-bot:
[integration/config@master] Clean out jsonlint/jshint

https://gerrit.wikimedia.org/r/349439

For most repositories, I have removed the jshint job that ran an outdated version of jshint. Most repos are thus now just invoking "npm test".

hashar claimed this task.

The Jenkins job that runs jshint has been removed from all the repositories. They now solely run npm test and whatever developers have defined in their repo.