© 2010 Intland Software
1
Refreshing Software Development
with
Distributed Version Control Systemen (DVCS)
ALMConf 2010, O...
© 2010 Intland Software 2
Intland & Background
• 2000 - founded by formal Cygnus (RedHat) employees
• 2010 - Intland Softw...
© 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
Status
check
...
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
codeBeamer
Agile ALM
Budapest Be...
Integration workflow example
© 2009 Intland Software 9
Release
repository
developer
local
developer
local
Integration
mana...
Why DVCS?
• Offline commits
• Fast local operations
• Results:
– More robust for distributed teams
– Fine-grained commits
...
untrusted-
repository
Automotive electronic supply-chain workflow example
© 2009 Intland Software 11
Release
repository
Au...
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
Upcoming SlideShare
Loading in …5
×

Refreshing Software Development with DVCS

787 views

Published on

Intland Software's Presentation at ALMConf 2010 in Stuttgart, October 26 - 28

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
787
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Jolt Award
  • Refreshing Software Development with DVCS

    1. 1. © 2010 Intland Software 1 Refreshing Software Development with Distributed Version Control Systemen (DVCS) ALMConf 2010, October 26 – 28, Stuttgart Janos Koppany Intland Software
    2. 2. © 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 Collaborative Tool Extensions Collaborative Tool Extensions Integrations SCMs, IDEs Integrations SCMs, IDEs Prof. Services Prof. Services ALM + Collaboration ALM + Collaboration
    3. 3. © 2010 Intland Software 3 … and further Fortune 500 customers
    4. 4. codeBeamer - Agile ALM © 2010 Intland Software 4 development methods: V-Model ,Agile, Scrum codeBeamer
    5. 5. © 2010 Intland Software 5 Thinking on the old “Centralized” Way Reqs. Reqs. Reqs. Reqs. Report Report Report Status check Status report Status report Status report Status report Test plan Test plan Test plan Test plan DokumenteDokumente Dokumente Dokumente DokumenteDokumente Dokumente Dokumente DokumenteDokumente Dokumente Status check Status check Mails Mails Excel Excel Excel Mails Mails MailsExcel
    6. 6. The World is flat, Intland’s Distributed development © 2010 Intland Software 6
    7. 7. Distributed v.s. Centralized VCS © 2009 Intland Software, Sebastien Auvray 7
    8. 8. Stuttgart Deployment infrastructure with GIT/Mercurial, Eclipse © 2010 Intland Software 8 codeBeamer Agile ALM Budapest Beijing, Taipei Git/Mercurial Repositories Developer Workstation: •Windows/Linux (VMWARE) •Eclipse + Intland’s Mercurial plug-in •Mercurial •Web browser Simbirsk
    9. 9. Integration workflow example © 2009 Intland Software 9 Release repository developer local developer local Integration manager developer public developer public
    10. 10. 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
    11. 11. untrusted- repository Automotive electronic supply-chain workflow example © 2009 Intland Software 11 Release repository Automotive electronic break subsystemnavi subsystem Sub- contractor Sub- contractor Sub- contractor Sub- contractor •open-source compliance check •code review
    12. 12. Eclipse screenshot – HgEclipse & CBES © 2010 Intland Software 12
    13. 13. Agile Scrum, Kanban process © 2010 Intland Software 13
    14. 14. CodeBeamer UI © 2010 Intland Software 14
    15. 15. MercurialEclipse project @Javaforge.com © 2010 Intland Software 15

    ×