© 2010 Intland Software1

Refreshing Software Development

with

Distributed Version Control Systemen (DVCS)

ALMConf 2010, October 26 – 28, Stuttgart

Janos Koppany Intland Software

© 2010 Intland Software 2

Intland & Background

• 2000 - founded by formal Cygnus (RedHat)

employees

• 2010 - Intland Software is the leading provider of

enterprise-class collaboration solutions that boost

the productivity of development and business

projects.

• 350.000+ users worldwide

codeBeamer

ParticipatecodeBeamer

Participate

Source Code Engineering

Features

Source Code Engineering

Features

CollaborativeTool

Extensions

CollaborativeTool

Extensions

IntegrationsSCMs, IDEs

IntegrationsSCMs, IDEs

Prof. Services

Prof. Services

ALM+

Collaboration

ALM+

Collaboration

© 2010 Intland Software 3

… and further Fortune 500 customers

codeBeamer - Agile ALM

© 2010 Intland Software 4

development methods: V-Model ,Agile, Scrum

codeBeamer

© 2010 Intland Software 5

Thinking on the old “Centralized” Way

Reqs.

Reqs.

Reqs.

Reqs.

Report

Report

Report

Statuscheck

Statusreport

Statusreport

Statusreport

Statusreport

Testplan

Testplan

Testplan

Testplan

DokumenteDokumente

Dokumente

Dokumente

DokumenteDokumente

Dokumente

Dokumente

DokumenteDokumenteDokumente

Statuscheck

Statuscheck

MailsMails

Excel

Excel

Excel

Mails

Mails

MailsExcel

The World is flat, Intland’s Distributed development

© 2010 Intland Software 6

Distributed v.s. Centralized VCS

© 2009 Intland Software, Sebastien Auvray 7

Stuttgart

Deployment infrastructure with GIT/Mercurial, Eclipse

© 2010 Intland Software 8

codeBeamerAgile ALM

Budapest Beijing, Taipei

Git/MercurialRepositories

Developer Workstation:•Windows/Linux (VMWARE)•Eclipse + Intland’s Mercurial plug-in•Mercurial•Web browser

Simbirsk

Integration workflow example

© 2009 Intland Software 9

Releaserepository

developerlocal

developerlocal

Integrationmanager

developerpublic

developerpublic

Why DVCS?

• Offline commits

• Fast local operations

• Results:

– More robust for distributed teams

– Fine-grained commits

– Searchable history

– Branching and merging is a natural task ->

– Better workflows -> processes

© 2010 Intland Software 10

untrusted-repository

Automotive electronic supply-chain workflow example

© 2009 Intland Software 11

Releaserepository

Automotiveelectronic

break subsystemnavi subsystem

Sub-contractor

Sub-contractor

Sub-contractor

Sub-contractor

•open-source compliance check•code review

Eclipse screenshot – HgEclipse & CBES

© 2010 Intland Software 12

Agile Scrum, Kanban process

© 2010 Intland Software 13

CodeBeamer UI

© 2010 Intland Software 14

MercurialEclipse project @Javaforge.com

© 2010 Intland Software 15