The Art of Scaffolding
summary
Shows how temporary automation—often simple Perl scripts that fetch builds from a sketchy location—lets teams run OpenJDK 11 tests before the official pipeline exists, so developers find and fix failures earlier and projects like Eclipse OMR, OpenJ9 and AdoptOpenJDK keep moving. Describes three failure modes: hacking that never scales, scaffolding that collapses too soon, or scaffolding that lingers as extra maintenance. Success looks like unblocked dev teams, running tests, and a community that returns.
AI-written summary · about
related talks
46mIt’s Never a Technology Problem: Using Experience to Solve the Problem
37mFrom Rigidity to Resiliency: An Evolutionary Tale of Selenium-Based Frameworks
34mAdoptOpenJDK: Ensuring Free Java for the Community
25mBad Behaviour: Automating System-level Safety Testing Using Open Source Tools
05mThe Slings and Arrows of Open Source
51mCommon pitfalls in engineering teams and how to avoid them
35mThe Social Coding Contract
27m(Re)building a Framework: Lessons, Community, and Impostor Syndrome