something like:
{nav icon=code-fork, name=Changeset uploaded to Differential >
icon=ship, name=run Harbormaster build plan >
icon=cogs, name=call gearman api >
icon=sitemap, name=nodepool (on Gallium) >
icon=cogs, name=CI job runner (labs instance) >
icon=code-fork, name=clone the repo from phabricator >
icon=stethoscope, name=run tests >
icon=heartbeat, name=report test results (via conduit) >
icon=cog, name=differential test status updated }
So first we need to unblock the gearman port for {nav iridium > gallium} and then write a trivial script to enqueue build details via the gearman api.
Personally I feel like it would be cleaner if gallium offered an http api that phabricator could call directly from harbormaster's existing configurable http rest client, however, some sort of gearman client in phabricator won't be too hard to build.