If you check in code and merge it haphazardly into the main branch of whatever source control system you are using, errors may prevent the build process that sets the web app to run. Your changes? You "broke the build", temporarily preventing your colleagues from doing any work on that shared project. This is a minor problem... unless you merged in your code just before going home. If that happened, you just prevented anyone who wanted to work the late shift from getting any work done.
If only there was some type of sign, some type of visual cue that the build was broken!
Tuesday night, during the Ministry of Testing - Boston's Lean Coffee, Andreas Grabner, a Technology Strategist at Dynatrace, showed us that there was.
Imagine: You finally solved the problem you had been working on all day, merged your code, and packed up for the day. Heading for the exit, you see this:
 |
| "Look! It's a Sign! A Sign that We Are Hosed!" |
Turn around. Go back to your desk. Your code broke the build. You need to go fix it.
This is the Dynatrace DevOps Pipeline State UFO.
 |
| Andreas demonstrates the UFO for Ministry of Testing - Boston |
As Andreas explains it in his March 6, 2017 article, Using the Dynatrace DevOps Pipeline State UFO, "The Dynatrace DevOps Pipeline State UFO was built out of the necessity to visualize alerts, problems, health and CI/CD pipeline state within the Dynatrace R&D organization. It sparked a cultural transformation as it made code quality that we pushed more frequently through our Delivery Pipeline more visible".
 |
| Taken from https://www.dynatrace.com/blog/using-dynatrace-devops-pipeline-state-ufo/ |
You can:
- 3D Print Your Own UFO: https://github.com/Dynatrace/ufo
- Pre-order Your Own UFO: https://www.dynatrace.com/solutions/devops/ufo/get/
Thank you, Andreas!
-T.J. Maher
Twitter | LinkedIn | GitHub
// Sr. QA Engineer, Software Engineer in Test, Software Tester since 1996.
// Contributing Writer for TechBeacon.
// "Looking to move away from manual QA? Follow Adventures in Automation on Facebook!"
3 comments:
Thanks for sharing these insights from the Lean Coffee session! The idea of using 'UFOs' as a signal for broken builds is both clever and effective. It's a great reminder of how communication plays a crucial role in maintaining a smooth workflow. I'm looking forward to implementing some of these strategies in our team discussions. Keep up the great work. baltimore sex crime lawyer
This is such a clever and engaging analogy! Using “UFOs” as a way to spot broken builds is a fun, memorable way to address a critical issue in development. It’s so true that teams often need clear, immediate signals when something goes wrong, and creative solutions like this can improve response time. I love that this Lean Coffee session explored ways to make build status visible and accessible for everyone—simple, effective indicators can save so much time and frustration. Thanks to Ministry of Testing-Boston for always bringing fresh ideas to the table! divorce lawyer in fairfax
fairfax divorce lawyer
To signal that a building is broken or in need of repair, it’s important to clearly communicate the issue for safety and awareness. Start by marking visible signs such as damaged walls, broken windows, or faulty doors with clear warning signs or barriers to prevent entry. If it's a structural issue, display notices to inform people about potential hazards, like uneven floors or unstable ceilings.
chapter 7 bankruptcy lawyers near me
truck accidents attorneys
Post a Comment