Process Improvement in Distributed Software Development  Using Eclipse with Mercurial or Git  Eclipse Summit 2010 © 2010 I...
Intland Software <ul><li>Intland Software is provides collaborative ALM solutions. </li></ul><ul><li>Intland is driving di...
Why DVCS? <ul><li>Offline commits </li></ul><ul><li>Fast local operations </li></ul><ul><li>Results: </li></ul><ul><ul><li...
Working with Centralized VCS system © 2010 Intland Software Shared Repository developer developer developer Centralized sy...
IT infrastructure with Mercurial/Git & Eclipse Chicago © 2010 Intland Software codeBeamer ALM, collaboration Munich Beijin...
Integration workflow with DVCS © 2010 Intland Software Release repository developer local developer local Integration mana...
Automotive electronic sub-system workflow example untrusted-repository © 2010 Intland Software Release repository Automoti...
Status <ul><li>Project URL: Javaforge.com </li></ul><ul><li>Version: 1.7, it is used in production </li></ul><ul><li>Free ...
Live Demo: xPhone 4 integration to automotive electronic Stutgart-1 © 2010 Intland Software JavaForge.com Issue management...
Upcoming SlideShare
Loading in …5
×

Eclipse summit-2010

619 views

Published on

How to Improve Your Geographically Distributed Software Development Process Using Eclipse With Mercurial and Git

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

  • Be the first to like this

No Downloads
Views
Total views
619
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Eclipse summit-2010

  1. 1. Process Improvement in Distributed Software Development Using Eclipse with Mercurial or Git Eclipse Summit 2010 © 2010 Intland Software Janos Koppany, Michael Lukas Intland Software GmbH
  2. 2. Intland Software <ul><li>Intland Software is provides collaborative ALM solutions. </li></ul><ul><li>Intland is driving different Eclipse / DVCS related open source projects: </li></ul><ul><ul><li>EclipseMercurial plug-in </li></ul></ul><ul><ul><li>codeBeamer ALM for Eclipse, Git, Mercurial </li></ul></ul>© 2010 Intland Software Collaboration Engine
  3. 3. Why DVCS? <ul><li>Offline commits </li></ul><ul><li>Fast local operations </li></ul><ul><li>Results: </li></ul><ul><ul><li>More robust for distributed teams </li></ul></ul><ul><ul><li>Fine-grained commits </li></ul></ul><ul><ul><li>Searchable history </li></ul></ul><ul><ul><li>Branching and merging is a natural task </li></ul></ul><ul><ul><li>Better workflows -> processes </li></ul></ul><ul><ul><li>Simplified Archivation </li></ul></ul>© 2010 Intland Software
  4. 4. Working with Centralized VCS system © 2010 Intland Software Shared Repository developer developer developer Centralized systems (SVN, CVS, CC, ..) -Windows/Linux -Eclipse + Subclipse -Web browser
  5. 5. IT infrastructure with Mercurial/Git & Eclipse Chicago © 2010 Intland Software codeBeamer ALM, collaboration Munich Beijing Git/Mercurial Repositories <ul><li>Developer Workstation: </li></ul><ul><li>Windows/Linux (VMWARE) </li></ul><ul><li>Eclipse + Git/Mercurial plug-in </li></ul><ul><li>Git/Mercurial </li></ul><ul><li>Web browser </li></ul>✔ ✔ ✔ ✔
  6. 6. Integration workflow with DVCS © 2010 Intland Software Release repository developer local developer local Integration manager developer public developer public
  7. 7. Automotive electronic sub-system workflow example untrusted-repository © 2010 Intland Software Release repository Automotive electronic break subsystem navi subsystem Sub-contractor Sub-contractor Sub-contractor Sub-contractor <ul><li>open-source compliance check </li></ul><ul><li>code review </li></ul>
  8. 8. Status <ul><li>Project URL: Javaforge.com </li></ul><ul><li>Version: 1.7, it is used in production </li></ul><ul><li>Free SaaS on Javaforge.com for open source projects </li></ul><ul><li>License: Open Source, EPL, free </li></ul><ul><li>Contact: www.intland.com </li></ul>© 2010 Intland Software
  9. 9. Live Demo: xPhone 4 integration to automotive electronic Stutgart-1 © 2010 Intland Software JavaForge.com Issue management, collaboration EC2 Cloud Darmstadt-2 Git/Mercurial Repositories <ul><li>Developer Workstation: </li></ul><ul><li>Windows/Linux/MAC (VMWARE) </li></ul><ul><li>Eclipse eGit + Intland’s Mercurial plug-in </li></ul><ul><li>Git/Mercurial </li></ul><ul><li>Web browser </li></ul><ul><li>PR Manager Workstation: </li></ul><ul><li>Windows/MAC </li></ul><ul><li>Web browser </li></ul><ul><li>Developer gets new task and implements </li></ul><ul><li>Developer commits changes, and change the issue status “Implemented” </li></ul><ul><li>Developer push changes to “JavaForge” … </li></ul>

×