-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On build failure, Harbormaster is not notified. #26
Comments
Can you post the build logs? Are you properly passing the PHID string parameter? |
Here's the harbormaster build logs:
|
Looks like I don't have permission to view the text. Could you paste me the output of the build log? |
Also, does the job have String parameters for PHID and DIFF_ID (or perhaps they're being ignored?). Only way to tell is to see the build output |
Well, the build is broken for reasons I recently put into #19, but I'll paste a larger version here: Usage Exception: This command requires arc to connect to a Phabricator install, but no
[phabricator] Unable to parse JSON from response:
[phabricator] Unable to parse JSON from response: |
I have the same failure for my patch https://code.uberinternal.com/D114594 https://code.uberinternal.com/D114594. Thanks,
|
Simon, will you please file a ticket on internal phab and assign it to me On Saturday, June 6, 2015, szhou1234 notifications@github.com wrote:
|
Aiden, Here it is: https://code.uberinternal.com/T101709 https://code.uberinternal.com/T101709 Thanks,
|
So after properly configuring my instance to get source from the git repo with a correct uri, this works on both success and failure of the job. I think in the future there should be some URI settings for Jenkins so it doesn't have to rely on proper .arcconfig to update Phabricator, but instead prefer information from one if available. Since my part in this is done, and Simon has his own ticket elsewhere, I'm going to close this. Thanks again! |
Having now restarted Harbormaster builds on my setup many times, I have noticed a trend that when the build fails (now every time, see #19), it does not send back a failure message to harbormaster. Instead Harbormaster patiently waits for the callback on that build and gives a status of "Building".
The text was updated successfully, but these errors were encountered: