GTAC 2013: Finding Culprits Automatically in Failing Builds - i.e. Who Broke the Build?
From Google TechTalks · 21:18
Show by Google TechTalks
http://g.co/gtac2013Slides: http://goo.gl/q9dGdCelal Ziftci, University of California, San DiegoVivek Ramavajjala, GoogleContinuous build is one of the key infrastructures in Google. When a build fails, it is vital to pinpoint the culprit changelist (CL)/changelists quickly, so that it can be fixed to get the build back to green.Culprit detection solutions exist for small and medium sized builds, but not for large integration builds.Uploaded 29-04-13Our culprit finder targets finding the culprit CL for large builds automatically, in a very short time-frame with high success. Based on production usage on multiple projects in the last 9 months, culprit finder provides very promising results. Come see our talk to see how we implemented the culprit finder, how successful it is in production and what it feels and looks like.
More episodes of Google TechTalks
More episodes
- The Limits and Possibilities of One Run Auditing
- PhotoTechEDU Day 29: Photographing VR Panoramas
- Privacy Ripple Effects from Adding or Removing Personal Information in Language Model Training
- Inside VMware Fusion
- Java Posse Episode 100 (Live Special)
- Cascading Adversarial Bias from Injection to Distillation in Language Models
- Practical Common Lisp
- Cascading Adversarial Bias from Injection to Distillation in Language Models
- Security is Broken
- POPri: Private Federated Learning using Preference-Optimized Synthetic Data
PodSearch is a free, independent podcast search engine. Read about PodSearch, the privacy policy or contact us.