There is a URI artifact type, so if you're writing your own custom build step in PHP, you can create a URI artifact that points to the CircleCI plan:

https://secure.phabricator.com/diffusion/P/browse/master/src/applications/harbormaster/storage/build/HarbormasterBuildArtifact.php;189fb2660a905c7d683cc312af66ca2065bc51d5$16

Hi @nornagon -- would you be willing to post details of you have your "excessive hacks" configured? I would love to have a similar setup at my company.

@dpaola2 at this point I don't even remember all the things I had set up, but it involves this monstrosity running on heroku:

Yikes! Thanks!

I'm going to wait until the Harbormaster doc gets split up a bit before writing details on how to use this, but here's the rough version.

After D13900 + D13903, you'll use harbormaster.createartifact(...) to publish a "uri" artifact as soon as your external build server (e.g., in Jenkins) receives a request and knows what the external build detail URI is. You'll use these parameters:

• buildTargetPHID: The build target PHID from Phabricator, same value you're using with harbormaster.sendmessage.
• artifactKey: Any unique name, like "jenkins.uri"
• artifactType: The string literal "uri".
• artifactData: A dictionary like this one:

{
  "uri": "http://your.build-server.com/build/details/12345232/",
  "name": "View Build Details in Jenkins",
  "ui.external": true
}

The ui.external key tells Harbormaster that this URI artifact is an external link which should be shown in the UI when build targets are rendered:

For example, this is a complete, valid call to add a link to Bing! to a build target:

$ echo '{
  "buildTargetPHID": "PHID-HMBT-bwxike43bzahut64duk5",
  "artifactKey": "link.bing",
  "artifactType": "uri",
  "artifactData": {
    "uri": "http://bing.com",
    "name": "Bing! It!",
    "ui.external": true
  }
}' | arc call-conduit --conduit-uri <your-phabricator-uri> --conduit-token <conduit-token> harbormaster.createartifact

The Conduit API page for the call (/conduit/method/harbormaster.createartifact/) is greatly expanded after those changes land, too.

Overall, your Jenkins thing will look something like:

// Publish the link to the external result page.
conduit.harbormaster.createartifact(...);

// Run the tests.
result = run_some_tests();

// Publish the test results.
conduit.harbormaster.sendmessage(result);

You can add several links if you want, they just each need to have unique keys (jenkins.detail-uri, jenkins.summary-uri). You should probably also give them unique names so humans can tell them apart.

Awesome! Thanks @epriestley :)