how we make unity

COPYRIGHT 2015 @ UNITY TECHNOLOGIES

HOW WE MAKE UNITY

A Look into How Development in Unity’s R&D Organization Works


A LOOK BACK


Text Styles

between levels

Level 1 = Bullet 24 pt. Level 2 = Bullet 24 pt. Level 3 = Bullet 20 pt. Level 4 = Bullet 18 pt. Level 5 = Bullet 16 pt.

again, use SHIFT + TAB

Alternatively,

OTEE ca. 2005 (around Unity 1.0 release)


Text Styles

between levels



Alternatively,

Unite Copenhagen, October 2008


Text Styles

between levels



Alternatively,

Unite San Francisco, October 2009


Text Styles

between levels



Alternatively,

Unite Montreal, November 2010


Text Styles

between levels



Alternatively,

Unite San Francisco, August 2011


Text Styles

between levels



Alternatively,

Unite Amsterdam, August 2012

COPYRIGHT 2014 @ UNITY TECHNOLOGIESCOPYRIGHT 2015 @ UNITY TECHNOLOGIES

AND NOW UNITY TECHNOLOGIES HAS OVER 650 EMPLOYEES.


HUNDREDS OF DEVELOPERS IN OVER 15 LOCATIONS ACROSS 4 CONTINENTS ALL WORKING TOGETHER.

BUT HOW?


• Na’Tosha J. Bard • Engineering Tools Lead at Unity

Technologies (5+ years) • Copenhagen, Denmark • Open-Source & Linux Enthusiast • Married • 2 cats

ABOUT THE SPEAKER


PRINCIPLES OF DEVELOPMENT AT UNITY


EMPOWERMENT AUTONOMY RESPONSIBILITY


THE LIFECYCLE OF A CHANGE


Text Styles

between levels



Alternatively,

Developer Commits Change

Developer Pushes Change

Build Server Verifies Build

with a Subset of

Build & Test Targets

Domain Experts Peer

Review Code

Gatekeeper Confirms

Build Verification and Code Review

Gatekeeper Merges

Change to Mainline

Build Server Verifies Build with All Build

& Test Targets

Build Server Makes

Release Build

QA Performs

Acceptance Test

Change Goes to External Testers

Change is Released!


VERSION CONTROL LOW-LEVEL BUILD AUTOMATION HIGH-LEVEL BUILD AUTOMATION CODE REVIEW AUTOMATED TESTING


VERSION CONTROL


REVISION CONTROL COLLABORATION MULTIPLE LINES OF DEVELOPMENT


Text Styles

between levels



Alternatively,

MERCURIAL• Switched from Subversion to Mercurial in 2010 • Branch-based development (named branches) • Extensions: largefiles, eol • Lots of custom Mercurial-based infrastructure • Active member of open-source community


Text Styles

between levels



Alternatively,

“TRUNK” REPOSITORY METRICS

• 37,323 normal files, 378 largefiles • 13 GB of metadata • 14 GB working copy (populated) • 196,699 revisions (255,895 in development repo) • 3831 named branches (7151 in development repo)


BRANCH-BASED DEVELOPMENT


Text Styles

between levels



Alternatively,

“trunk” (mainline)

feature branches

bugfix branches

release branches


BUT REALLY, IT’S IMPOSSIBLE TO EXPRESS THE COMPLEXITY WITH A SIMPLE PICTURE.


LOW-LEVEL BUILD AUTOMATION


Text Styles

between levels



Alternatively,

PLATFORM SUPPORT


22 PLATFORMS MULTIPLE ARCHITECTURES MULTIPLE VARIANTS


Text Styles

between levels



Alternatively,

EVOLUTION OF LOW-LEVEL BUILD SYSTEM• Pre-2011: Static project files w/ Perl scaffolding • 2011-now: Jamplus w/ Perl scaffolding • Future: Gradle

• https://youtu.be/jmadc8xI_6I


Text Styles

between levels



Alternatively,

EDITOR BUILD TIMES• MacBook Pro (Retina, 15-inch, Mid 2015)

• 2,8 GHz Intel Core i7 • 16 GB 1600 MHz DDR3 • SSD

• Clean Build: 5m50.097s • No-Op:

• Perl: 0m28.320s • Jam: 0m2.476s


HIGH-LEVEL BUILD AUTOMATION


239 POSSIBLE BUILD & TEST TARGETS 39 HIGH-LEVEL TARGETS IN A BUILD VERIFICATION 97 NIGHTLY TEST RUNS BUILD CHAINS MANY LAYERS DEEP


Text Styles

between levels



Alternatively,

KATANA• Internally-developed custom CI solution • Fork of Buildbot • https://github.com/Unity-Technologies/katana • Active development


Text Styles

between levels



Alternatively,

KATANA’S BUILD FARM• 236 (mostly virtual) machines

• Combination of local storage and NFS • Moving to CEPH

• Currently all hosted in Copenhagen • iOS farm with iOS team in Vilnius

• Configured with Salt


CODE REVIEW


IMPROVE CODE QUALITY APPLY EXPERT KNOWLEDGE HELP DOMAIN EXPERTS RETAIN OWNERSHIP KNOWLEDGE TRANSFER


Text Styles

between levels



Alternatively,

KALLITHEA• Open-Source source code management system • Supports Mercurial and Git • Web-based code review

• Preview of Merge • Pull Requests do not update automatically

• http://kallithea-scm.org


AUTOMATED TESTING


NATIVE TESTS RUNTIME TESTS INTEGRATION TESTS GRAPHICS TESTS MANY OTHER TESTS

16,559,749TESTS RUN IN AUGUST 2015


GATEKEEPER WORKFLOW


WHY USE A GATEKEEPER WORKFLOW IN A COMPANY FULL OF SMART, CAPABLE ENGINEERS? BECAUSE HUMANS ARE HUMAN.


OBJECTIVITY CONSISTENCY CONTINUITY


STUFF I’VE LEARNED ALONG THE WAY


FEAT

URE

SET

TIME

QUALITY


CHANGE IS A CONSTANT. OPPOSING FORCES ARE A GOOD THING. SOFTWARE DEVELOPMENT IS ABOUT SO MUCH MORE THAN WRITING CODE.


Text Styles

between levels



Alternatively,

Slides will be available at:

http://natoshabard.com/speaking

Find me at the Ask-the-Experts area, or on Twitter:

@natosha_bard