[JIRA] (JENKINS-44869) Activity tabs Run id column should expand to fit value

[r.fuereder@xortex.com (JIRA)]

Reinhold Füreder updated an issue

Jenkins / JENKINS-44869 Activity tabs Run id column should expand to fit value Change By: Reinhold Füreder Priority: Minor Major Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[r.fuereder@xortex.com (JIRA)]

Reinhold Füreder commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value James Dumay As I almost filed a duplicate of this issue: any updates/progress/hope?

Add Comment

[tony.hoyle@rpssoftware.co.uk (JIRA)]

Tony Hoyle commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

Even our (relatively) short build numbers eg '9.0.2.19007' don't fit in the current layout.  The tooltip works but it's annoying as there's no way to see the information in a quick glance. Could a quick fix just be to make it configurable by a parameter somewhere until the 'proper' fix is done?   Ideally in the future resizeable by dragging in the UI, but I guess that depends on the capabilities of the javascript library in use.

Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

[r.fuereder@xortex.com (JIRA)]

Reinhold Füreder commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

James Dumay Any updates on this issue? I claim this little issue is really, really worth being solved, or at least a workaround could be potentially very cheap to implement? Naive workaround for calculation of table column width: int width = Math.max(<currentWidth of I think 92px>, Math.min(maximumWidth that should not be exceeded which may be ~250>, <width needed for full display of latest build display name because that might be the biggest build number or in my use case just about as long as all the others>)

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[tscherler@cloudbees.com (JIRA)]

Thorsten Scherler commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

Reinhold Füreder are you using https://wiki.jenkins.io/display/JENKINS/Version+Number+Plugin or https://wiki.jenkins.io/display/JENKINS/Build+Name+Setter+Plugin

Add Comment

[r.fuereder@xortex.com (JIRA)]

Reinhold Füreder commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

Thorsten Scherler Actually I am not using any of these plugins, but I have a little helper method in my Jenkins shared pipeline library that does it "directly": /*script.*/currentBuild.displayName = ...

Add Comment

[r.fuereder@xortex.com (JIRA)]

Reinhold Füreder commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

Naively pinging Thorsten Scherler and Michael Neale to politely ask for considering this issue as it might be a very low hanging fruit for an IMHO major BO usability improvement... (Presumably others will classify this as "getting on one's nervers" )

Add Comment

[mneale@cloudbees.com (JIRA)]

Michael Neale commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

Gavin Mogan Nicolae Pascu is his something to consider as a quickie?

Add Comment

[jmcdonald@cloudbees.com (JIRA)]

Josh McDonald commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

It's not really as easy to fix as it first seems, as browsers really take some time to let you know the size of things, and if you change the sizing of one of their containing elements in response to same, you invalidate all the sizes of everything again and you risk the potential for endless loops and constantly shimmying controls, which nobody wants

Add Comment

[r.fuereder@xortex.com (JIRA)]

Reinhold Füreder commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

Thanks for your considerations and thoughts; and also sorry for my naiveness... However, with respect to your hints regarding problems of dynamics: Would it be possible to really do this statically in that the column width is calculated/fixed before the rendering, based on the width needed for rendering solely either the current or maybe the previous build's ID (plus a small tolerance) and of course not exceeding (i.e. limited to) a maximum value to avoid breaking the layout completely?

Add Comment

[mneale@cloudbees.com (JIRA)]

Michael Neale commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

I don't think it would know the size until after something has been rendered, and then then the browser can take it's sweet time.    However, given we know what ids normally are, if they are anything but numeric in the data set returned - perhaps could just change the width to something that is "probably" wide enough for those cases (99% of people will be numeric and fine)? A really brain dead heuristic.

Add Comment

[gmogan@cloudbees.com (JIRA)]

Gavin Mogan commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

Yea, as above mentioned, its not a quick easy win. The tables are pretty fixed with, and I think changeing the run id is a pretty niche item.    That being said, fixing JENKINS-46521 might help so that the commit id is no longer -, and would no longer be needed in the build id? maybe?

Add Comment

[r.fuereder@xortex.com (JIRA)]

Reinhold Füreder commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

Oh yes, this sounds like a great idea: hiding the "Commit" column for a non-multi branch pipeline in favour of showing the full build display number in the BO's activity tab "Run" id column (see JENKINS-44869) would be ideal/fine for me because I have the commit ID (SVN revision or shortened GIT commit hash) as suffix of my therefore quite long build display number, e.g. "20170613-161100-rev134098" (i.e. "<date>-<time>-rev<SVN revision>")

Add Comment

[mneale@cloudbees.com (JIRA)]

Michael Neale commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

Reinhold Füreder having trouble following - any chance you can mock it up what it may look like in your case?

Add Comment

[r.fuereder@xortex.com (JIRA)]

Reinhold Füreder updated an issue

Jenkins / JENKINS-44869

Activity tabs Run id column should expand to fit value

Change By: Reinhold Füreder Attachment: screenshot-now.png

Add Comment

[r.fuereder@xortex.com (JIRA)]

Reinhold Füreder updated an issue

Jenkins / JENKINS-44869 Activity tabs Run id column should expand to fit value

Change By: Reinhold Füreder Attachment: screenshot-future.png

Add Comment

[r.fuereder@xortex.com (JIRA)]

Reinhold Füreder commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value Michael Neale Sorry for the confusion. I referred to Gavin Mogan's comment and JENKINS-46521 Mock up: Now/old: Future/new:

Add Comment

[peter.niederlag@datenbetrieb.de (JIRA)]

Peter Niederlag commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

does anybody have a solution yet? I'd like to see the RUN column to take up more space (1.5x or 2x)

Add Comment

[ironchamp@gmail.com (JIRA)]

Alan Champion commented on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

Complementary to JENKINS-46657 allowing currentBuild.displayName, where the RUN column is no longer just #1-1000, this needs to accommodate typical build/release names, which potentially may be prefixed by target environment and/or dynamic job status. So, having 30-35 chars is needed to see the distinction; otherwise it is inconsistent with expectations and virtually useless.

Add Comment

[ironchamp@gmail.com (JIRA)]

Alan Champion edited a comment on JENKINS-44869

Re: Activity tabs Run id column should expand to fit value

Complementary to JENKINS-46657 allowing currentBuild.displayName, where the RUN column is no longer just simply #1-1000, this now needs to accommodate typical build/release names, which potentially may be prefixed by target environment and/or dynamic job status. In our system, using the MESSAGE column description as an "alternative" is inadequate, as this shows "Started by <user>/upstream job" or "Replayed #?". So, having 30-35 chars the expectation is needed to see that RUN column shows the distinction; otherwise  *full* currentBuild.displayName buildName, whatever width it is inconsistent with expectations and virtually useless needs to be . Thanks for your attention to this detail.

Add Comment