Page MenuHomePhabricator

Make artifacts imply dependencies on build steps
ClosedPublic

Authored by hach-que on Jul 31 2014, 2:03 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, May 3, 10:35 AM
Unknown Object (File)
Thu, Apr 25, 3:55 AM
Unknown Object (File)
Sat, Apr 20, 3:22 PM
Unknown Object (File)
Mon, Apr 8, 11:10 AM
Unknown Object (File)
Apr 1 2024, 9:53 AM
Unknown Object (File)
Apr 1 2024, 4:58 AM
Unknown Object (File)
Mar 29 2024, 4:28 AM
Unknown Object (File)
Mar 4 2024, 11:06 PM
Subscribers

Details

Reviewers
epriestley
Group Reviewers
Blessed Reviewers
Commits
Restricted Diffusion Commit
rP0f355756f5ca: Make artifacts imply dependencies on build steps
Summary

This makes input artifacts imply the appropriate build step dependencies in the build plan. That is, if you use a host artifact in a build step, it will then implicitly depend on the 'Lease Host' step.

Test Plan

Viewed the build plan with the artifacts, saw the dependencies. Ran a build, saw everything execute in the correct order.

Diff Detail

Repository
rP Phabricator
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

hach-que retitled this revision from to Make artifacts imply dependencies on build steps.
hach-que updated this object.
hach-que edited the test plan for this revision. (Show Details)
hach-que added a reviewer: epriestley.
epriestley edited edge metadata.
epriestley added inline comments.
src/applications/harbormaster/step/HarbormasterBuildStepImplementation.php
121

This should probably be array_merge(...), in case an artifact eventually has a numerical key which collides with a natural key in dependsOn.

This revision is now accepted and ready to land.Jul 31 2014, 2:15 AM
hach-que edited edge metadata.

Use array_merge

hach-que updated this revision to Diff 24266.

Closed by commit rP0f355756f5ca (authored by @hach-que).