Page MenuHomePhabricator

Change "lint save" to not use Arcanist Projects
ClosedPublic

Authored by joshuaspence on May 18 2015, 12:32 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 17, 1:29 PM
Unknown Object (File)
Fri, Dec 13, 2:46 AM
Unknown Object (File)
Tue, Dec 10, 6:08 AM
Unknown Object (File)
Mon, Dec 9, 12:06 PM
Unknown Object (File)
Sat, Dec 7, 1:41 PM
Unknown Object (File)
Thu, Dec 5, 3:20 AM
Unknown Object (File)
Wed, Dec 4, 10:14 PM
Unknown Object (File)
Sat, Nov 30, 7:44 AM
Subscribers

Details

Summary

Ref T7604. Change DiffusionLintSaveRunner to use repositories instead of Arcanist Projects.

Test Plan

Ran the save_lint.php script and queried results using the diffusion.getlintmessages Conduit endpoint.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

joshuaspence retitled this revision from to Change "lint save" to not use Arcanist Projects.
joshuaspence updated this object.
joshuaspence edited the test plan for this revision. (Show Details)
joshuaspence added a reviewer: epriestley.
epriestley edited edge metadata.
This revision is now accepted and ready to land.May 18 2015, 1:28 PM

It looks like arcanist calls the conduit endpoint with arcanistProjectPHID... so perhaps we need to keep this parameter around for a while?

Oh -- it only does if you pass --only-new, which I think is very, very rarely used. I don't think we need to retain compatibility too carefully. Just shoot me a diff to swap the call?

src/applications/diffusion/DiffusionLintSaveRunner.php
67

Maybe this should be changed to be $this->actor and then the omnipotent user is set via setActor.

src/applications/diffusion/DiffusionLintSaveRunner.php
67

In the long run, the design of this is weird, anyway, in the context of modern CLI scripts. I think we should move it into bin at some point and make it (CLI) Workflow-based (e.g., bin/repository import-symbols), when it gets a getViewer() automatically (which just evaluates to the omnipotent user). Fixing it up in advance of that is fine, but maybe not worth bothering with.

This revision was automatically updated to reflect the committed changes.