-
Notifications
You must be signed in to change notification settings - Fork 258
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
ball-<size> not working #40
Comments
Hi @jeannich, thank you for your feedback. I have one question: Can you please check if this is also happening when the job is NOT in running state? Thank you, |
Hi @thomas-dee , I confirm the issue happens also when job is NOT running. The URL pointed by the images seems fine though. |
Ok @jeannich, thank you. This is interesting since for me it is working fine... for both cases. What browser are you using? |
Thanks for the follow up @thomas-dee No idea if it is related but you must know that my jenkins setup has a tiny issue. It has no effect on my intense usage of jenkins though. |
@jeannich Well, exactly that might be the reason for the issue. The "Jenkins URL" ("Manage Jenkins" -> "Configure System") needs to be set to the URL you use to access Jenkins in your browser. |
Same issue here. I am using a reverse proxy, too, but it is configured correctly and Jenkins does not complain. When trying to access the ball-icon, i get a 404. The other styles work fine. |
Maybe related: The protected "Text-Only" badge also gives me a 404. The unprotected one works fine. |
@thomas-dee indeed when setting my jenkins URL to "https://foo:8443/" (instead of just "https://foo/") it works. I can see the bullets. Still I find this strange as every other plugins and personal scripts are working fine with just "https://foo/". There seem to be a round trip in this plugin to get bullet status. Maybe you could double check if there is something that can be improved in this plugin here? Thanks for the support ! |
@jeannich Thanks for the input. You are right, there is a "round trip" to get the bullets. The thing is, that the Jenkins API provides an "external" reference (i.e. URL) for the Jenkins balls. I haven't found out (yet) how to get the balls via internal reference. Another way would be to "just copy" the current ball images and serve them by myself. But I'd like to do it the other way. |
ok @thomas-dee , I'll let you decide what to do with this topic. Again, thanks for the support |
We're seeing this issue as well ... looking at the network panel in chrome it's reporting the request for Same with the other example ball style ... the regular rectangular badges are fine though ... We do use the http://wiki.jenkins-ci.org/display/JENKINS/Green+Balls plugin though ... wonder if that is having an effect? Edit: Confirming that the Green Balls plugin is what causes the issue with us, removing it displayed the images properly. Unfortunately I suspect I'll get push back on removing it... any chance to enable some sort of compatibility here? |
Hello, |
I don't have Green Ball plugin and I don't have any proxies, also Jenkins URL is set correctly (tried machine's hostname, fqdn both with and without :443) - balls are not rendered. Jenkins version 2.289.3 on windows server. Also I'm pretty sure previous versions of jenkins had the very same issue, so it's a definitely long lasting bug. |
We're having this also. What I noticed is that the |
Hey,
Any idea ? Thanks in advance, Cyril |
Hi,
I am using "Embeddable Build Status" V2.0 in Jenkins 2.150.3, running on Linux.
With this setup, the ball- feature it is not working ; balls are not rendered at all.
The text was updated successfully, but these errors were encountered: