Page MenuHomePhabricator

Can an alternate drydock (something other than /var/drydock) area be configuable for drydock working copies/builds?
Closed, DuplicatePublic

Description

After wading through initial configuration (which is slightly confusing right now) of Almanac/Drydock/Harbormaster I ran into a problem that prevents us from using this to run builds.

Basically we have code we would like to run our test suite for every commit, but due to requiring access to software/tools/resources we must run in a shared environment where creating /var/drydock is difficult/impossible. Ideally our working copies/running area for drydock would be something like $HOME/var/drydock so that a non-privileged automation account could pull from our Phabricator host and run our build.

Also I noticed that if a resource fails to activate (in this case, a working copy) it will retry indefinitely, it didn't really cause trouble but it seems like the build should have failed instead of trying 50+ times to get a resource?