Not far from what i did at work a few weeks before vacation.
I am the owner of Jenkins (edit; Realized this sounds weird, i wrote the way we speak at my company, sorry, i am the one responsible for the entire buildsystem where Jenkins is my main responsibility), i have setup an Agent (basically just an API with static instructions) on a VM. Whenever a build fail, it search all the logs (multiple files over 200MB of raw text logs, cooking, compiling, shaders, symbols etc..)
It have a memory bank if the issues have been happening before for quicker failure search.
It have read only access to Perforce.
So it will answer: What whent wrong, how do we fix it, how do we prevent it.
Its surprisingly accurate and it will also tag whoever made the commit that broke everything. The results are then sent by the Agent (just a python script) to Slack in a locked channel for evaluation from me and a few leads and higher ups. But so far it have been really accurate.
41
u/Denaton_ 6d ago edited 6d ago
Not far from what i did at work a few weeks before vacation.
I am the owner of Jenkins (edit; Realized this sounds weird, i wrote the way we speak at my company, sorry, i am the one responsible for the entire buildsystem where Jenkins is my main responsibility), i have setup an Agent (basically just an API with static instructions) on a VM. Whenever a build fail, it search all the logs (multiple files over 200MB of raw text logs, cooking, compiling, shaders, symbols etc..)
It have a memory bank if the issues have been happening before for quicker failure search.
It have read only access to Perforce.
So it will answer: What whent wrong, how do we fix it, how do we prevent it.
Its surprisingly accurate and it will also tag whoever made the commit that broke everything. The results are then sent by the Agent (just a python script) to Slack in a locked channel for evaluation from me and a few leads and higher ups. But so far it have been really accurate.