ball-<size> not working

[jenkinsci]

ball- not working

from embeddable-build-status-plugin.

[hogarthj]

We're seeing this issue as well ... looking at the network panel in chrome it's reporting the request for https://server.fqdn/job/project/job/repo/job/branch/badge/icon?style=ball-16x16 as text/plain with a 0byte HTTP 200 response ...

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?

[thomas-dee]

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,
Thomas

[jeannich]

Hi @thomas-dee , I confirm the issue happens also when job is NOT running.

The URL pointed by the images seems fine though.
I have this:
https://..../job/MyJobName/badge/icon?style=ball-16x16
https://..../job/MyJobName/badge/icon?style=ball-32x32

[thomas-dee]

Ok @jeannich, thank you. This is interesting since for me it is working fine... for both cases.

What browser are you using?

[jeannich]

Thanks for the follow up @thomas-dee
I tested on Chrome, IE, Edge and Firefox: same result.

No idea if it is related but you must know that my jenkins setup has a tiny issue.
I have this error message in Configuration pane:
"It appears that your reverse proxy set up is broken."

It has no effect on my intense usage of jenkins though.
My jenkins server is hosted on a Tomcat started on port 8443, then I use an iptable rule to connect external port 443 to internal 8443.

[thomas-dee]

@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.

[ChristianCiach]

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.

[ChristianCiach]

Maybe related: The protected "Text-Only" badge also gives me a 404. The unprotected one works fine.

[jeannich]

@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?
@ChristianCiach 's comment tends to convince me there might be something doable on plugin side.

Thanks for the support !

[thomas-dee]

@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.

[jeannich]

ok @thomas-dee , I'll let you decide what to do with this topic.
Keep it as a 'bug', or switch it to enhancement request or some other treatment.

Again, thanks for the support
bests

[feraudet]

Hello,
I've same issue without Green Ball plugin :/

[xCharg]

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.

[jeroenlandheer]

We're having this also. What I noticed is that the Content-Type of the image isn't set, which cases the browser to refuse to render it. (We have X-Content-Type-Options: nosniff set as a security measure.)