copy build status URL from Jenkins branch/job page

[jenkinsci]

copy build status URL from Jenkins branch/job page

[MarkEWaite]

Thanks for the suggestion @jkatnik . I need some further clarification on what you'd like to see improved.

Are you suggesting that we should replace the current input field that shows the sample embedded status URL with a text string that has a "copy button" near it? That would be something like the copy button that is included in the Jenkins design library plugin as shown on the tooltips example page. That's something that has annoyed me recently, since the input field that is being used today is really not an input field at all.

Today's page

Future page

With apologies that I did this with a few seconds of image copy and paste

Further clarification needed

When you say that a build status icon could be included on the Jenkins branch page and on the job page, I'm not sure how you envision that would work. How would the user know that content they were copying was the embeddable build status URL? How would the user decide which form of the embeddable build status URL should be copied?

I'm a frequent user of the markdown format version of the build status URL. However, I don't know which type of URL is preferred by most users, so would not know which type of URL to be copied with that copy button.

[jkatnik]

Hi @MarkEWaite

thanks for taking an interest in my request.

To depict my idea I implemented this feature as a tampermonkey script.

The downside of it is that everyone needs to have the Tampermonkey addon and the script installed. I'm not sure if your plugin can modify the Jenkins Job history page, but if does then it wouldn't have had that flaw.

JenkinsBuildStatus.mp4

[MarkEWaite]

I think you can already do that with the Markdown Formatter plugin and adding a snippet to your job description. I'm a little surprised that they want it on that page, rather than looking at the results that are already visible on the page, but here's how I place a summary of key jobs (specific branches of specific multi-branch Pipelines) on a top level folder. I see very quickly when one of the key jobs is not stable with this:

[jkatnik]

The Markdown Formatter plugin looks promising however, Admins in my organization hesitate to install new Jenkins plugins because they are worried about Jenkins stability.

If you find this feature obsolete, then there is no problem - for my needs the script workaround is enough.

Have a nice evening :)

[MarkEWaite]

If the admins allow you to embed safe HTML in the description, you don't need the markdown formatter plugin. The HTML from the embeddable build status plugin can be placed inside the job description as well. I find it easier to read markdown than HTML, but understand that there are plenty of organizations that prefer HTML over markdown.

[MarkEWaite]

I'm going to close this one as "Won't do" because it would be too wide an impact on too many users.