Page MenuHomePhabricator

Migrate "Run Command" to use Drydock hosts
ClosedPublic

Authored by hach-que on Dec 5 2013, 2:50 AM.
Tags
None
Referenced Files
F16392351: D7707.diff
Mon, Jun 16, 12:51 AM
Unknown Object (File)
Thu, May 29, 2:21 AM
Unknown Object (File)
Wed, May 28, 6:37 PM
Unknown Object (File)
Tue, May 27, 6:45 PM
Unknown Object (File)
Apr 25 2025, 6:50 PM
Unknown Object (File)
Apr 25 2025, 2:26 AM
Unknown Object (File)
Apr 24 2025, 5:41 PM
Unknown Object (File)
Apr 24 2025, 10:55 AM

Details

Summary

This migrates the "Run Remote Command" build step over to use Drydock hosts and Harbormaster artifacts.

Test Plan

Created a build plan with a "Lease Host" step and a "Run Command" step. Configured the "Run Command" step to use the artifact from the "Lease Host" step.

Saw the results:

{F87377}

{F87378}

Diff Detail

Branch
execute-on-artifact
Lint
Lint Passed
SeverityLocationCodeMessage
Advicesrc/applications/harbormaster/step/CommandBuildStepImplementation.php:119XHP16TODO Comment
Unit
No Test Coverage

Event Timeline

src/applications/harbormaster/config/PhabricatorHarbormasterConfigOptions.php
6

bwahaha

src/applications/harbormaster/config/PhabricatorHarbormasterConfigOptions.php
15–32

{burnittotheground}

15–32

Macro burnittotheground:

Nice!

src/applications/harbormaster/step/CommandBuildStepImplementation.php
47

These are OK for now, I think Drydock predates the widespread use of PolicyQuery.