Project Description
Since we use different systems to report bugs (Bugzilla) and track their fixes (GitHub), we have a dedicated tool to keep our boards in sync and up-to-date between those two. The tool we use today is called finglonger and it's written in clojure which makes it rather difficult to maintain and expand.
Goal for this Hackweek
The minimum goal for this hackweek is to create a minimal working client capable of matching BZ bugs with the GH issues the way the finglonger does it. The maximum goal is to rethink the basic functionality and come up with some new ideas on how to make life of RRBG easier.
Resources
This project is part of:
Hack Week 21
Activity
Comments
Be the first to comment!
Similar Projects
openQA log viewer by mpagot
Description
*** Warning: Are You at Risk for VOMIT? ***
Do you find yourself staring at a screen, your eyes glossing over as thousands of lines of text scroll by? Do you feel a wave of text-based nausea when someone asks you to "just check the logs"?
You may be suffering from VOMIT (Verbose Output Mental Irritation Toxicity).
This dangerous, work-induced ailment is triggered by exposure to an overwhelming quantity of log data, especially from parallel systems. The human brain, not designed to mentally process 12 simultaneous autoinst-log.txt files, enters a state of toxic shock. It rejects the "Verbose Output," making it impossible to find the one critical error line buried in a 50,000-line sea of "INFO: doing a thing."
Before you're forced to rm -rf /var/log in a fit of desperation, we present the digital antacid.
No panic: The openQA Log Visualizer (Also known as the "VOMIT-B-Gone 9000")
This is your web-based hazmat suit for handling toxic log environments. It bravely dives into the chaotic, multi-machine mess of your openQA test runs, finds all the related, verbose logs, and force-feeds them into a parser.
Goals
Work on the existing POC openqa-log-visualizer and change it to something usable
Resources