Friday, 13 June 2014 13:00 @ Room 1
Like any good developer, you take pride in your work. So it’s no surprise that you’re dedicated to the cause of code quality and continuous integration. Thanks to a dark-arts blend of JUnit, TestNG, and Selenium, you’re built a deflector shield that keeps bugs at bay.
And then it happened: your team decided to switch to Git. CI was challenging enough when you just had trunk and a release branch. But with the sudden explosion of active branches, things can feel downright chaotic. You may find yourself asking deep existential questions such as “Do I really have to run CI on all those branches?” or “Ouch, it hurts! How can ease this excruciating pain?” and “Can we ever regain the tight culture of quality we had in the SVN days?”
This talk will answer all those questions, and more. (Spoiler alert: the answer to the first question is yes. Probably.) Learn how to apply CI to all your branches without making your eyes bleed or clogging up the build queue, and how Git hooks help maintain release-ready quality in your code without nag-mails or awkward conversations at the water cooler.
It’s a brave new world out there… better Git ready for it.