Component Management Migration from Clearcase to SVN - SubConf 2010

Resources / SVN

84 views
0 Likes
0 0
The UBS Wealth Management & Business Banking unit migrated its internal software development projects from the CM Synergy (formerly Continuus) change management system to Subversion. In this talk, we present organizational and technical aspects of the migration project. We show how existing development processes were adapted and how user acceptance for the new system was achieved. Furthermore, we discuss the technical challenges involved in the migration of a large number of CM Synergy repositories to Subversion.

Share on Social Networks

Share Link

Use permanent link to share in social media

Share with a friend

Please login to send this presentation by email!

Embed in your website

Select page to start with

4. Who is Elster Kromschröder? (1)

6. Who is Elster Kromschröder? (3)

12. What is component management? (3)

13. What is component management? (4)

27. Questions?

15. Which use cases were adressed by the project? (1)

16. Which use cases were adressed by the project? (2)

18. Which software components were used? (1)

20. Which software components were used? (3)

22. Which software components were used? (5)

24. Which software components were used? (7)

11. What is component management? (2) ● A Release is a set of components with specific versions which should be compatible with each other

1. Component management for embedded systems via Subversion ® and addons - report on successful migration from ClearCase ® UCM Manuel Blechschmidt – SubConf 2010 – Munich

19. Which software components were used? (2) ● Visual SVN Server 2.1.1 ● Patched pysvn 1.7.2 extensions ● TortoiseSVN 1.6.8 ● with JIRA plugin

10. What is component management? (1) ● A component is a software package, a web service or a module that encapsulates a set of related functions or data ● It has well defined interfaces which can change during versions ● It can have dependencies to other components in specific versions

23. Which software components were used? (6) ● Python 2.6.5 ● Patched pysvn 1.7.2 ● ZSI Beta 2.1 Web Services Layer ● difflib ● SimpleHTTPServer

26. What lessons were learned? ● Open standards make the integration of independent systems possible ● Good documentation makes people happy and software usable ● Default installations never fullfil your requirements ● It never works the first time

2. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?

3. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?

7. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?

9. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?

14. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?

17. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?

25. Agenda ● Who is Elster Kromschröder? ● What was the project? ● What is component management? ● Which use cases were adressed by the project? ● Which software components were used? ● What lessons were learned?

21. Which software components were used? (4) ● JIRA 4.0.2 ● Connected to Active Directory ● Enabled WebServices ● Plugins ● Extended WebServices ● Subversion Plugin

8. What was the project? ● Replace current Component Management Solution ClearCase with Subversion ● Make all changes in a project traceable ● Provide tooling support for all common actions ● Establish a best practice workflow which can be used as an example for other departments ● Use a central installation which can be scaled across the whole company

5. Who is Elster Kromschröder? (2) Site Elster Kromschröder Hameln ● Development ● Production ● Quality management ● Service Development ~10 People Software Configuration Management for ● Development ● Service (planned)

Views

  • 84 Total Views
  • 58 Website Views
  • 26 Embedded Views

Actions

  • 0 Social Shares
  • 0 Likes
  • 0 Dislikes
  • 0 Comments

Share count

  • 0 Facebook
  • 0 Twitter
  • 0 LinkedIn
  • 0 Google+