Fix console parallel stages overflow

[LakshyaBagani]

Fixes #16806

When parallel pipeline stages have long names, the branch labels in the console output overflow into the left sidebar, making them hard to read and overlapping with navigation items.

The Pipeline plugin uses ::before pseudo-elements with position: absolute and transform: translateX(-100%) to position these labels in the left margin. This fix overrides that behavior to display labels inline instead.

Testing done

Created a pipeline job with parallel stages having long names and ran it multiple times. Checked the console output page before and after the fix:

• Before: Labels like [run echo hello world from step 1] were positioned in the left margin and overflowed into the sidebar
• After: Labels appear inline with the console text, no more overflow

Also verified that regular console output (non-pipeline) still works correctly.

Screenshots

Before

After

Proposed changelog entries

• Fix pipeline parallel branch labels overflowing into sidebar in console output

Proposed changelog category

/label bug,web-ui

Proposed upgrade guidelines

N/A

Submitter checklist

• The issue, if it exists, is well-described.
• The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• UI changes do not introduce regressions when enforcing the current default rules of Content Security Policy Plugin. In particular, new or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@timja @MarkEWaite @mawinter69

[mawinter69]

wrong place I would say. That is something that should be fixed in pipeline (not sure which plugin exactly) and not here. When pipeline decides to use a different class (although unlikely), the fix would no longer work.

[LakshyaBagani]

I placed this change in core because it already handles .console-output styling, and the pipeline-node-* naming has been stable for years since it’s based on internal node IDs. Given that, it didn’t feel worth doing a separate plugin release just for this.

Would you prefer that I move these changes to the plugin instead ?

[timja]

this should be done in pipeline not here, a pipeline class doesn't make sense to be in core

[mawinter69]

Having this in the plugin has the advantage that all you need is a plugin update and not a Jenkins update. So all users of pipeline benefit from it also that are not on the latest Jenkins. Consider that it will take weeks until this change reaches a LTS version.

[LakshyaBagani]

Since changes in plugins can be rolled out faster, I’m going to close this PR . Thanks for the feedback .

[LakshyaBagani]

@mawinter69 @timja
Could you please let me know which repository these plugins come from, so I can contribute there to fix this issue?