-
Notifications
You must be signed in to change notification settings - Fork 14
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
Proper setup guide? #21
Comments
That is very strange. What version of Jenkins and the JRE are you running, and what version of the plugin are you on? |
I'm on openjdk-8 and Jenkins 1.643. The plugin is on 1.8.3. Firstly I thought it was due to no service listening to that port (14740), then I double checked:
Just to be clear, what exactly should I set for the instance location? e.g. |
Try changing the |
So if I don't put http:// in front of the ip address for instance location, I get the following error
If I do, I get
I also tried useing it with mysql so the listening address was 0.0.0.0, so I don't think that's the cause. |
Based on the output you've pasted above, it's only listening on the loop And yes, you do need http://
|
I've just tried your suggestions and change the bind port to another, but still getting
This might be a silly question - do i need set up something else (e.g. a webserver) along with this? |
Ah, the 404 is expected, it means there is no coverage data available. You
|
Alright I'll give it a try and get back to you. Thanks! |
Also there is a duplicated key error when using either sqlite or mysql.
It also keeps getting 404 errors no matter how many polling builds or direct non-diff builds on master - so looks like connection is not the issue as it's getting responses back, but I don't think it's posting anything to sqlite/mysql.
Query mysql tables after several builds (both direct and polling) gives
|
Interesting, a 404 should not happen on sending coverage data unless the server isn't listening properly. You're running it directly, correct (no nginx/apache/varnish doing reverse proxying)? |
Yea that's what I mentioned above (service isn't listening), but I double checked and made sure the uberalls server is up and listening to 8080. One thing to mention is that the our phabricator, jenkins and the coverage server all run in within the same local network but phabricator and jenkins have their own public https url. Could that be causing the problem? |
I just ran netstat -tulpn on the coverage server and turned out uberalls is listening on 8080 via tcp6. Could that be the problem? |
Potentially, yea, although I'm a bit mystified how that would be the case if you specified an IPv4 listen address. |
I see the same in the log
Still setting up jenkins jobs, will update how it goes. |
I have exactly the same problem. It also shows the same message in the log and Jenkins keep giving `
I did run the build first via SCM polling, and have configured the uberalls url in Jenkins to 192.168.0.108:14741 I can go to 192.168.0.108:14741/health, giving me ;-). Is there any solution on this matter? |
I'm also seeing
|
Resolved my problem -
|
@rphilipsen in case you haven't resolved your problem yet, I believe you need to set Uberalls url to |
IMO uber-archive/phabricator-jenkins-plugin#256 needs to be fixed as well for this to be considered stable. Running the job on a cron is useless and shouldn't be required. |
So I've been trying to set up this, my steps as follow
The app starts successfully and listens to 14740 and use sqlite in this case. Then I set the location of the uberalls instance to a local ip address, let's say 192.168.1.100:14740 in Jenkins, and did a baseline run building on the trunk (master in this case). Up til this setp everyting works fine and Jenkins sends non-diff to phabricator (e.g.
[phabricator:non-differential] Sending coverage result
).But when I started another differential build, I got the following errors:
I've also tried different protocals for the location instance, e.g. with and without http://, with or without port number, but so far no luck.
Could you shed some light on this?
The text was updated successfully, but these errors were encountered: