Harbormaster actions (such as the build passing) used to be part of the differential timeline: https://cloud.githubusercontent.com/assets/1963030/9352309/97d1ed7a-4660-11e5-91ad-41646222c850.png
What I am doing a now is a lot of testing and re-starting builds. Form differential the only way to tell that a new build finished is that the artifact url (T8659) has changed. The buildable itself has a timeline, but that just shows the most recent status and when I restarted it, but not the history of pass/fails. This is moderately annoying when debugging builds and restarting them a lot, although I do not expect that to be the common case.
I'm **worried** about cases like:
* R: Hey the code looks okay but why does test X fail?
* A: (hits button) No they pass.
* R: `¯\_(ツ)_/¯`
or
* R: Please fix x.
* A: (fixes x, some flakey test fails)
* R: Wait did the tests fail before?
But I have not used Harbormaster enough 'for real' to run into those. I'm also unsure if the 'just put it in the timeline' approach is viable when a diff kicks off multiple builds.
Related chatter:
* https://github.com/uber/phabricator-jenkins-plugin/issues/80
* https://secure.phabricator.com/chatlog/channel/6/?at=211713