Details
-
New Feature
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Duplicate
-
None
Description
Split from discussion in JENKINS-41200. Briefly, the failure to support standard ConsoleNote in Blue Ocean causes various problems; for example, if you use the ANSI Color plugin to colorize build output in the classic UI, this explodes in Blue Ocean. In general, lots of plugins use console notes for all sorts of reasons, and none of them work in B.O. Would be desirable to at least support basic inline HTML tags which should not in principle mess around with the different page layout in B.O. mode.
Attachments
Issue Links
- relates to
-
JENKINS-43107 Support console annotations and log stuff
-
- Resolved
-
-
JENKINS-41200 Developer can see ANSI color in log file
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue relates to |
As described in the original issue, if you try to use the ANSI Color wrapper, the classic build log looks nice, but Blue Ocean shows no colors; if you do not use it, then Blue Ocean is colorized, but the classic build log is full of unreadable junk (unprocessed escape sequences).
Again, this is just one example of the broader issue of B.O. not supporting the standard Jenkins console API.
| Assignee | Vivek Pandey [ vivek ] |
| Sprint | Blue Ocean 1.3 - beta 1 [ 386 ] |
| Epic Link | JENKINS-35759 [ 171771 ] |
| Link |
This issue relates to |
| Assignee | Vivek Pandey [ vivek ] |
| Sprint | Blue Ocean 1.3 - beta 1 [ 386 ] | Blue Ocean 1.4 [ 311 ] |
| Comment |
[ The standard "console api" is a total disaster, having had a closer look. The logs are mutated in ways that strip the original ansi colours, and if one is to remove plugins... (josh has a write up). They are just terrible, terrible things. More investigation needed. Blue ocean is not going to inject random html made by these things. ] |
The ansi color wrapper removes the actual ansi color codes, so will be a PR to fix that specifically.
| Link |
This issue relates to |
| Sprint | Blue Ocean 1.5 - candidates [ 311 ] |
| Rank | Ranked higher |
This is a no for the same reasons outlined in JENKINS-43107.
Ill follow up on the ansi color issue.
| Link |
This issue relates to |
| Resolution | Duplicate [ 3 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Any updates on the ansicolor issue? This become the No1 reason that prevents adoption of the blueocean UI: nobody wants to lose ansicolor. I am in a position when nobody wants to use blueocean because lack of coloring and where I cannot disable ansibecolor on old ui.
We really need a solution that works for both user interfaces.
ssbarnea no one has been able to work out a solution that works for both (after spending a week on it), so it may not be possible at this time. Or bigger brains than mine are required... (highly likely)
Background doc on how complex this all is based on early jenkins design decisions: https://docs.google.com/document/d/1wIBYfU734c4CU45l_EZMwKAqoVeQL3SsbzQhESoYWI4/edit#heading=h.4kdft5qo8ksb
Perhaps if ansicolor would not strip the codes - it could work in both, but the classic view would need to know to strip them somewhere else (just thinking aloud) - if you were only interested in ANSI working in both? (or are there other notes?)... perhaps...
sigh
**Maybe some bigger brains than mine can find a solution? But jenkins logging was never designer other than for the original view of the log (server side rendering with fixed markup, log mutation via plugins that can't be uninstalled or the log data looks broken). If ANSI color is most of it though... perhaps there is hope? It's a tought place to be in.. more brains needed.
jglick in what way does it blow up?
Unfortunately injecting any elements that way is going to not play with react nicely.