We could use a job triggered by all repositories that would enforce some basic checks. Typically linting PHP/json, i18n banana checker ...
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T40233 Jenkins: Fail on BOM in submitted files | |||
| Declined | None | T67140 Prevent the addition of files with names that aren't supported on Windows | |||
| Resolved | Umherirrender | T94547 Configure banana checker for i18n files to run on all MediaWiki extensions and skins | |||
| Resolved | greg | T92531 add a check for whitespace before leading <?php | |||
| Declined | None | T101511 common job for all repositories that runs structural linting | |||
| Declined | None | T111181 use one job for all CI entry points |
Event Timeline
Comment Actions
I have set them the over way but seems to me whenever we get that common job implemented that will fix all the blocking tasks :-}
Comment Actions
From the CI weekly meeting on Sept 29th 2015.
Seems we could have a central Makefile in integration/config.git. Then have the repositories trigger a single job make-test that would invoke our central Makefile.
The Makefile will automatically detect what kind of commands it can run and do it. For example run npm test when there is a package.json file in the repo.
Comment Actions
As this ticket is more about generic checks like is the commit message ok. I created T111181 for the above comment.
Comment Actions
Change 242177 had a related patch set uploaded (by Hashar):
Generic test runner entry point
Comment Actions
The rough idea was https://gerrit.wikimedia.org/r/242177 . However it is nicer for now to have jobs run in parallel.