CI Build Log Error Extractor (GitHub Actions, Jenkins, GitLab)
Strips colours and timestamps, finds the first failing line and shows context.
Use the tool
Why this tool exists
A failed build log can run to thousands of lines, and the cause is somewhere near the first error. This tool jumps there and shows the lines around it, plus the step name when the log has groups.
It uses a list of strong error patterns for GitHub Actions, npm, TypeScript, Jest, Maven, Python, Git and shell. The first failing line is not always the root cause.
How to use it
- Copy the raw log from the CI run.
- Paste it or open the file.
- Set lines of context before and after.
- Read the first failure and the list of other errors.
Frequently asked questions
Which CI systems work?
Any text log. Step names are read from GitHub Actions groups and Jenkins pipeline stages.
Why does it miss my error?
Tick the option to count lines containing the word error.
Are colours handled?
ANSI codes and leading timestamps are removed first.
Is my log uploaded?
No. Everything is processed in your browser and nothing is sent. Logs can hold IP addresses and tokens, so the page does not write them into the address bar.