Hi,
In true internet fashion this isn't the answer that you want, but
there's an NVDA add-on called BrowserNav that I've found goes some way
towards solving edit areas such as these, although we only use Jenkins
at work so don't have any direct experiences of the systems you
mention.
Have a look at the readme, in particular the "Editing semi-accessible
edit boxes" section:
https://github.com/mltony/nvda-browser-nav
My main issue with CI type logs is their length and lack of structure.
We had an interesting one a few months ago where the build was showing
as success which Jenkins defines as anything that finishes with exit
code 0. It was obvious from a sighted point of view that it had
failed, but because I was just going from the bottom up and seeing
success I missed it. I'd argue (and successfully did) that that's a
poorly configured job though.
As an aside, I'm in the very early stages of experimenting around
building an add-on that uses GPT to provide structure to large
quantities of output such as the ones we're dealing with. My initial
tests suggest that (privacy concerns aside) you can feed it the logs
and ask it to convert the output into HTML with a heading structure
that maps to the different sections of the log. It does it really well
for things like Python errors, NPM, Jest etc, then you just h your way
through it, so to speak.
Cheers,
Ben.
On 6/27/23, Andrew Hodgson
Hi.
Anyone got any tips for accessing the console output from a CI system job run? I'm talking about Azure Devops and Github Actions which both have the same issues.
I have fairly verbose jobs that I need to get info from fairly quickly. Back in the golden days I could open the console output from the job in Edge or whatever and do a find on page using JFW's find feature, and the piece of text I wanted would come up and I could arrow around to read the log.
These days both of these systems are doing something different. I typically can't just do a search anymore on the log window. In Azure Devops I can view a raw log, but it has timestamps which I have to skip through in order to get to what I want. In Github actions I have to download the log locally and go through it there. Arrowing through the log in the log viewer doesn't help either, I can sometimes turn off virtual PC cursor and get text out that way. Even worse is when I want to copy text from the log to the clipboard, its virtually impossible for me to select what I want and do ctrl+c to get it in the clipboard and elsewhere.
Anyone got any tips for navigating these systems? Thanks. Andrew. _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org