-
Notifications
You must be signed in to change notification settings - Fork 102
No comments or links posted back, just Harbormaster marked as failed #252
Comments
tcpdump -s 0 -vv -X 'tcp dst port 80'
Maybe I'll try to decode the data tomorrow. |
Hmm, I found it. Or something at least. In the build HTTP request artifacts section there is a link to the Jenkins build page.
So, something is making it back. Is this all that is expected from |
@altendky You should have comment with the link in your differential revision. |
@sascha-egerer, thanks for the response. In this case I am working with regular commits, not differential revisions. Should this work differently between the two? |
Well, I'm finally back on this task and still having the same issue. :] From the looks of it a non-differential request simply doesn't get to the commenting code. Below is only And only further down do we get to building the result and eventually calling Additionally, the defaults from I've got a start at some changes to enable comments for Diffusion in addition to Differential but it's not quite working for me yet. When I get there I'll share what I've got to see if it is all sensible. Of course, if someone else thinks they know how to handle this... I would appreciate any help I can get. :] Cheers, |
The easy explanation for Diffusion comment support not being implemented here is that you can't add comments to Diffusion via Conduit. https://secure.phabricator.com/T6461 I'm following up with the Phabricator team to discuss how to make the build links more readily accessible. |
I am trying to get a Phabricator/Jenkins docker-compose.yml going. It's a mess in various ways but 'close' to working finally. I am testing it only with commits at this point, no differentials.
I have installed the latest locally built
phabricator-jenkins-plugin
(0ba61e0). Phabricator is hooked to a private GitHub repo and using Herald to trigger Harbormaster to trigger Jenkins. I have apost {}
forPhabricatorNotifier
in myJenkinsfile
. It is setting the Harbormaster result to failed (the build is segfaulting in the image...:[
) so that's proper. But, I don't see a comment or link to the Jenkins build anywhere despite havingcommentWithConsoleLinkOnFailure: true
. I initially didn't have Arcanist installed but adding that didn't help.Any pointers on what debugging steps I should take?
Cheers,
-kyle
Since it seems similar I'll go ahead and reference #224.
The text was updated successfully, but these errors were encountered: