Page MenuHomePhabricator

Make PullLocal smart about which repositories it should pull
ClosedPublic

Authored by epriestley on Apr 11 2016, 4:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 29, 12:23 AM
Unknown Object (File)
Wed, Nov 27, 5:45 PM
Unknown Object (File)
Tue, Nov 26, 11:06 PM
Unknown Object (File)
Mon, Nov 25, 10:51 AM
Unknown Object (File)
Sun, Nov 24, 12:49 AM
Unknown Object (File)
Sat, Nov 23, 10:47 PM
Unknown Object (File)
Sat, Nov 23, 9:27 PM
Unknown Object (File)
Sat, Nov 23, 5:44 AM
Subscribers
None
Tokens
"Love" token, awarded by eadler.

Details

Summary

Ref T10756. When repositories are properly configured for the cluster (which is hard to set up today), be smart about which repositories are expected to exist on the current host, and only pull them.

This generally allows daemons to pretty much do the right thing no matter how many copies are running, although there may still be some lock contention issues that need to be sorted out.

Test Plan

Screen Shot 2016-04-11 at 9.43.39 AM.png (300×1 px, 135 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Make PullLocal smart about which repositories it should pull.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
  • Say "will not be updated on this host" instead of "will not be pulled", since this applies to hosted repositories too, and is sort of confusing if not qualified.
chad edited edge metadata.
chad added inline comments.
src/applications/almanac/controller/AlmanacDeviceViewController.php
241

thx

This revision is now accepted and ready to land.Apr 11 2016, 5:12 PM
This revision was automatically updated to reflect the committed changes.