[JENKINS-70778] Use modern build status icon instead of "ball-"

[jenkins-infra-bot]

The embeddable build status plugin still relies on the colored balls, as seen on https://ci.jenkins.io/job/Core/job/stapler/job/master/badge/ for example.

You can reference them via `ball-`.

However, Jenkins does no longer use colored balls to display a build status. The legend displays the different states of build statuses: https://ci.jenkins.io/legend

Instead of manually inserting the colored ball PNGs, the embeddable-build-status plugin should make use of the API, to display the appropriate build status icons, you can find in other occasions in Jenkins.

---

Originally reported by notmyfault, imported from: Use modern build status icon instead of "ball-"

• status: Open
• priority: Minor
• component(s): embeddable-build-status-plugin
• label(s): ui, ux
• resolution: Unresolved
• votes: 1
• watchers: 8
• imported: 20251210-235911

Raw content of original issue

The embeddable build status plugin still relies on the colored balls, as seen on https://ci.jenkins.io/job/Core/job/stapler/job/master/badge/ for example.

You can reference them via `ball-<size>`.

However, Jenkins does no longer use colored balls to display a build status. The legend displays the different states of build statuses: https://ci.jenkins.io/legend

Instead of manually inserting the colored ball PNGs, the embeddable-build-status plugin should make use of the API, to display the appropriate build status icons, you can find in other occasions in Jenkins.

[jenkins-infra-bot]

ompatel21:

• Original comment link
• Raw content of original comment:

  Hi notmyfault, I want to work on this issue. I am a newbie to this project so can you guide me though this improvement.
  

Hi notmyfault, I want to work on this issue. I am a newbie to this project so can you guide me though this improvement.

[jenkins-infra-bot]

notmyfault:

• Original comment link
• Raw content of original comment:

  Hey,
  
  Sounds great. Please consider using our chat channels, like the newcomer-contributors one, to ask questions.
  
  If you are looking for guidance with the UI, you can use the design library for reference or browser the source code of Jenkins: https://weekly.ci.jenkins.io/design-library/
  

Hey,

Sounds great. Please consider using our chat channels, like the newcomer-contributors one, to ask questions.

If you are looking for guidance with the UI, you can use the design library for reference or browser the source code of Jenkins: https://weekly.ci.jenkins.io/design-library/

[jenkins-infra-bot]

devrish:

• Original comment link
• Raw content of original comment:

  Couldn't recreate this issue. Tried building a freestyle project and found modern icons being used. Also, the only occurrence of "ball-" I found were present in two tests. Is this issue closed?
  

Couldn't recreate this issue. Tried building a freestyle project and found modern icons being used. Also, the only occurrence of "ball-" I found were present in two tests. Is this issue closed?

[jenkins-infra-bot]

amit4688:

• Original comment link
• Raw content of original comment:

  devrish could you please tell me how to contribute here as i'm aware of github how to contribute through that but this is Jenkins own website how can i contribute through this?
  
   
  

devrish could you please tell me how to contribute here as i'm aware of github how to contribute through that but this is Jenkins own website how can i contribute through this?

 

[jenkins-infra-bot]

devrish:

• Original comment link
• Raw content of original comment:

  amit4688  The code repositories that you need to contribute to are present on Github. This application is JIRA, it is used for keeping track of issues, not for code contribution. Check the `Component` information in the issue descripton, and search for the relevant repository under jenkinsci or jenkins-infra Github organisations.
  
  Any progress you make is to be discussed here, but the contribution is to be done on Github.
  

amit4688  The code repositories that you need to contribute to are present on Github. This application is JIRA, it is used for keeping track of issues, not for code contribution. Check the `Component` information in the issue descripton, and search for the relevant repository under jenkinsci or jenkins-infra Github organisations.

Any progress you make is to be discussed here, but the contribution is to be done on Github.

[jenkins-infra-bot]

felipecassiors:

• Original comment link
• Raw content of original comment:

  I would appreciate this improvement as well. This would make some internal markdown pages I have a lot nicer.
  
  Not to mention it would finally "fix" the successful color from blue to green.
  

I would appreciate this improvement as well. This would make some internal markdown pages I have a lot nicer.

Not to mention it would finally "fix" the successful color from blue to green.

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  felipecassiors I don't understand how you're using the embeddable build status plugin in a way that forces anyone to see the ball icons, other than you choosing to use those icons in the link that you embed.  The embeddable build status page for each build, like badge page of the plugin's own build shows many different examples that embed the build status without a ball icon.
  
  As an example, I've embedded the Confluence form of the status icon below
  
  
  
  Yes, the plugin continues to allow users to use a colored icon if they wish, but that is only retained in the plugin in order to not break compatibility with existing users.  I've embedded a Confluence example of the ball icon below to show that it is still operating as expected.
  
  
  

felipecassiors I don't understand how you're using the embeddable build status plugin in a way that forces anyone to see the ball icons, other than you choosing to use those icons in the link that you embed. The embeddable build status page for each build, like badge page of the plugin's own build shows many different examples that embed the build status without a ball icon.

As an example, I've embedded the Confluence form of the status icon below

Yes, the plugin continues to allow users to use a colored icon if they wish, but that is only retained in the plugin in order to not break compatibility with existing users. I've embedded a Confluence example of the ball icon below to show that it is still operating as expected.

[jenkins-infra-bot]

felipecassiors:

• Original comment link
• Raw content of original comment:

  markewaite I have a "Changelog" markdown page with a badge for each release, where the ball style aligns and looks much better than the flat style.
  
  So, I would prefer to stick with the ball style for the badges, but if the ball style was updated from the legacy to the modern icons, my markdown page would look a lot nicer.
  
  Regarding green vs blue, I solved by installing the Green Balls plugin (even though it's marked as deprecated/obsolete, it still works for this purpose).
  
  Please let me know if there's any confusion left.
  

markewaite I have a "Changelog" markdown page with a badge for each release, where the ball style aligns and looks much better than the flat style.

So, I would prefer to stick with the ball style for the badges, but if the ball style was updated from the legacy to the modern icons, my markdown page would look a lot nicer.

Regarding green vs blue, I solved by installing the Green Balls plugin (even though it's marked as deprecated/obsolete, it still works for this purpose).

Please let me know if there's any confusion left.

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  Thanks for the clarification.  I think that the plugin would need to be extended with a new capability to return the modern status image.  I don't think that the plugin should surprise other users by modifying the existing "ball" behavior, but should instead allow users to reference the modern status image through a different entry.
  

Thanks for the clarification.  I think that the plugin would need to be extended with a new capability to return the modern status image.  I don't think that the plugin should surprise other users by modifying the existing "ball" behavior, but should instead allow users to reference the modern status image through a different entry.

[jenkins-infra-bot]

felipecassiors:

• Original comment link
• Raw content of original comment:

  I agree, unless there are plans to deprecate the legacy balls in Jenkins, which I suspect to be true given the Green Balls plugin being marked as deprecated/obsolete.
  
  timja, since you worked on the new icons (Modernize build status and weather icons jenkins#5065), and basil, since you deprecated Green Balls, would you have any insight on whether the legacy icons will be deprecated/removed?
  

I agree, unless there are plans to deprecate the legacy balls in Jenkins, which I suspect to be true given the Green Balls plugin being marked as deprecated/obsolete.

timja, since you worked on the new icons (jenkinsci/jenkins#5065), and basil, since you deprecated Green Balls, would you have any insight on whether the legacy icons will be deprecated/removed?

[jenkins-infra-bot]

basil:

• Original comment link
• Raw content of original comment:

  would you have any insight
  
  I have no such insight
  

would you have any insight

I have no such insight

[jenkins-infra-bot]

felipecassiors:

• Original comment link
• Raw content of original comment:

  markewaite, as long as it is possible to retain the same functionality of the existing balls (e.g. can provide the same sizes as the existing balls to not break any design relying on these sizes), I would say all users would probably appreciate being "surprised" with the new design.
  

markewaite, as long as it is possible to retain the same functionality of the existing balls (e.g. can provide the same sizes as the existing balls to not break any design relying on these sizes), I would say all users would probably appreciate being "surprised" with the new design.