Description
Description
Details
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Phan jobs for libraries | integration/config | master | +38 -0 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Joe | T252745 Sandbox/limit child processes within a container runtime | |||
Resolved | tstarling | T260330 RFC: PHP microservice for containerized shell execution | |||
Resolved | Legoktm | T263295 Setup Git repo and CI for shellbox | |||
Resolved | hashar | T263313 Provide a job template for phan jobs for php libraries |
Event Timeline
Comment Actions
Change 628900 had a related patch set uploaded (by Hashar; owner: Hashar):
[integration/config@master] Phan jobs for libraries
Comment Actions
The jobs above run phan with php-ast which makes them faster. Then Phan has a pure PHP parser which works just fine, albeit being slower. @cscott
used that for mediawiki/services/parsoid and that looks like:
composer.json
{ "scripts": { "test": [ "@phan", }, "phan": "phan -p --allow-polyfill-parser --config-file=.phan/standalone.php --long-progress-bar", "phan-integrated": "phan -p --allow-polyfill-parser --long-progress-bar", }
Which might be fast enough for your use case :]
Comment Actions
Change 628900 merged by jenkins-bot:
[integration/config@master] Phan jobs for libraries
Comment Actions
Running phan from composer test is fine for us -- we just need to (apparently) make sure ext-ast is installed when running composer test.