We're planning to unprototype Drydock in the cluster soon (see parent task T10246). Before doing this, there are some technical and usability issues in Harbormaster and Drydock that I want to try to clean up.
- D15364 / rARCb1de04aa6836: Report unit test details from Arcanist to Harbormaster
D15393 / rPe6158391d27d: Make Drydock repository operations a little more modern and consistent
D15392 / rPfc0dc02bb92d: Allow Drydock blueprints to be tagged and searched, and give types some…
D15390 / rP1bdf9885562e: Convert DrydockBlueprints to EditEngine
D15389 / rP01379958fa3d: Allow Drydock blueprints to be searched by name
D15376 / rPe174cac1b476: Give HarbormasterBuildLogChunk a real table
D15375 / rP0daa9ad98758: Use PhutilRope as a buffer in Harbormaster BuildLogs
D15369 / rP8240e0f72706: Treat "skipped" unit tests as less interesting than "passed"
D15370 / rPHUad3f475c8c13: Make the libphutil library map test failure more readable
D15365 / rP181e030535f6: Give unit test results their own table in Differential
D15363 / rPd436fecdab19: Show additional details for failed builds in Harbormaster
D15362 / rP3c19b72ca0c8: Begin making Harbormaster unit test results a little easier to read
D15360 / rP5512e9724ff3: Allow Harbormaster build plans to be tagged with projects and searched by tag
D15359 / rPf078fd98d79b: Support searching for Harbormater build plans by name substring
D15357 / rP5295c6ba1e61: Use EditEngine for Harbormaster Build Plans, fix some crumbs/mobile stuff
D15355 / rPfdca684814da: Slightly improve Buildable list in Harbormaster
D15354 / rP220ac48801a1: Remove buildable handle / container handle logic form Harbormaster buildable…
- Mentioned In
- Blog Post: Development Notes (2016 Week 9)
T5822: Implement garbage collection / automatic archiving for Harbormaster logs
- Mentioned Here
- T7449: Support ANSI escaped color sequences in Paste
T8656: Parse ANSI-style color strings in build output
T10246: Deploy Drydock in the Phacility cluster
Is support of ansi color possible in this harbormaster iteration ? I mean not only parse the ansi code but also generate a markup based on the color.
As far as I remenber it wasn't the case.
Sometimes some information highlight are really usefull : in my ansible deploy (as a use case), they differentiate the log level.
But I understand if harbormaster console isn't the higher priority.
@epriestley : sorry, I should have searched more thoughtfully.
Is it something community can do ?
If so, where shall I start ?
So far, if my contribution can interest you, i would :
- first implement a ANSI parser that strip out ansi code (like [33m ) replacing it by U+FFF9 or U+FFFB depending if it is an ansi open code or an ansi close : this would be a PhutilMarkupEngine, right ?
- generate a syntax highlighter ( iw ould learn how to do it based on PhutilRainbowSyntaxHighlighter)
If you agree on this, I would open a new feature request task, and start diffing.