A Build Eco-System for Loosely Compiled Code
summary
Subversion commits trigger Jenkins via a post-commit hook to build only changed files from a 260 million‑line codebase across 15 released versions, largest app ~21,000 files. The pipeline uses a build-by-application model, a last build file plus a success marker to avoid missed or partial commits, and fixes for Windows certificate revocation and antivirus slowdowns. Translation and formatting checks run before deployment; failed builds send a Groovy-formatted email with a direct failure link. The result is reliable, incremental builds.
AI-written summary · about
chapters (6)
related talks
34mStaying Current A Journey in Software Maintenance
33mCI/CD for Autonomous Drive and other complex systems - What we have learned about...
22mShifting Left, Shifting Right
15mBetter Living Through sbt
31mStrengthen Our Developer eXperience to Face Obsolescence and View...
18mExtending Git without breaking it
25mKnowledge Transfer by Source Code
01h 23mManaging Modular Software for your NuGet, C++ and Java Development