Over a million developers have joined DZone.

Presenting on Trunk-based Development at the Perforce MERGE Conference

DZone's Guide to

Presenting on Trunk-based Development at the Perforce MERGE Conference

· DevOps Zone ·
Free Resource

Is the concept of adopting a continuous everything model a daunting task for your fast moving business? Read this whitepaper to break down and understand one of the key pillars of this model in Continuous Governance: The Guardrails for Continuous Everything.

This was a month ago at Perforce’s MERGE 2014 conference, but the videos are up now, so you can watch it too:

Trunk-based Development in the Enterprise, its Relevance and Economics

Of many case studies that I have, I detailed one where a hedge-bet on the order of releases paid off. Not that the client knew they were hedge-betting at the outset, that’s just the reality of Trunk Based Development, Feature Toggles / build switches, and Branch by Abstraction. Perhaps Application Strangulation too.

I couldn’t name the client, but they have many billions of dollars of revenue through the web-app in question.

For those with ADHD, the PPT is there too, and you can get through that in about 60 seconds if you do 2 seconds per slide!

Other presentations from MERGE you should watch.

If you’re spending the time on MERGE materials, Some are Trunk Based Development related, some are pure scale related (some both). I also have a “novel use” interest where VCS is the back-end, and a subset are listed below.

Working Well Together: How to Keep High-end Game Development Teams Productive

Presenter – Frank Compagner, Guerilla Games – a Sony subsidiary. Link to presentation.

Their HEAD revision of Trunk is 1.8 TB (1.6 million files), which the DON’T subset when they checkout to a developer workstation.

If I pasted everything of value from Frank’s presentation, I’d have every slide in here. Of his soundbites, one that I tweeted was gold:

“Branches create distance between developers and we don’t wan’t that”

What Continuous Delivery Means for Version Control

Jez Humble’s presentation is always going to be THE keynote for enterprise people. Jez and I had a minor struggle before the conference to make out presentations not overlap too much. I think we did OK. Link to presentation

Adidas’ Digital Platform for High Performance Creativity

Presenters: Alja ter Burg (adidas) and Jithin Chacko (Mindtree). Link to presentation

Version control in a designers workflow. Not web-developer / UX style designers, those that make shoes! Alja ter Burg speaks first on the addidas story and context up to the creation of a custom tool. Jithin Chacko follows with the “what we made” part of the story.

A great soundbite from Jithin:

“Our users are usually right brained people who don’t care if it is a versioning system or a file sharing system, they just want it to stay out of their way”

Version Your Cloud: Using Perforce to Manage Your Object Storage

Presenter: Daniel Anolik, Jeppesen, a Boeing Company. Link to presentation

Daniel details their novel use of Perforce to manage data for client applications, and end-users.

BDAM: Big Data Asset Management

Mark Harrison & Mike Sundy of Pixar

The listing from the agenda

Sadly, this was a “camera’s off” moment at MERGE. The amount of stuff these folks have under version control is truly incredible. If someone could leak their cameraphone footage to the web, I’d be so pleased – it was almost criminal that it wasn’t released. If it is only the clips from Toy story and Monsters Inc (etc) that was verboten, can we get those rectangles redacted please guys?

Similarly Doug Quist’s NVIDIA usage was eye opening, not from the conference as such, but Doug was there.

Are you looking for greater insight into your software development value stream? Check out this whitepaper: DevOps Performance: The Importance of Measuring Throughput and Stability to see how CloudBees DevOptics can give you the visibility to improve your continuous delivery process.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}