Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic SYNERGY (steve huntington)
Decrease font size
Increase font size
Topic Title: Migration process
Topic Summary:
Created On: 4-Aug-2003 20:41
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 4-Aug-2003 20:41
User is offline View Users Profile Print this message


Henock Gebreamlak

Posts: 3
Joined: 4-Aug-2003

Hello all, I am brand new to cm Synergy and am in the process of teaching myself.

Couple of questions:

Do you have to create and assign a task in order to Migrate a project for the very first time?

Once migrated, how do you verify what you did is right? (assuming you did not get error during the migration process)

Also, as a user how do I figure out my assigned role? developer, build_mgr, etc...

Thank you,

Henock

Report this to a Moderator Report this to a Moderator
 5-Aug-2003 11:28
User is offline View Users Profile Print this message


Pierre Guillet

Posts: 21
Joined: 4-Jul-2003

> Do you have to create and assign a task in order to Migrate a project for the very first time?

Yes it's better to do all your migration work with a task and also associate the task with all migrated object. If you want to use reconfigure with task, this avoids to have "No task" conflict on a Show conflict operation.


> Once migrated, how do you verify what you did is right? (assuming you did not get error
> during the migration process)

Your migrated tree is stored in a work area on your filesystem. You can do a recursive difference (diff -r on Unix or NT with Cygwin) between the work-area and the original directory. Warning: CM Synergy adds in work area an internal file (ccmwaid) don't delete it.
This diff is inly to check the project contents.

Be carrefull to the type association: a binary file must be migrated as an object with "binary" type (or a subclass) and not as "ascii" type (or subclass). You can have problem after migration (on check-in) if files have bad type or you can be limited (no difference can bone between binary objects).
On migrate preview, you can see these associations and you can click on edit to see the contents. Use "executable" to migrate an excecutable binary file, "shsrc" to migrate a script shell, "binary" for non ASCII file (files with non printable characters and long lines)...

One advise is to migrate the object as working (Tools>Migrate... Options>Set : Set object state to ... working)

> Also, as a user how do I figure out my assigned role? developer, build_mgr, etc...
Use build_mgr role to define the release.
Your roles are displayed in the interface. Use "ccm users" as ccm_root to change the list.
Use developer role to create the project and to migrate, to create and check-in the task.
Use build_mgr role to publish the migrated project (check-in on project to prep status).
Read the Build Manager's Guide RTFM;-)

Regards,







-------------------------
Pierre Guillet
Report this to a Moderator Report this to a Moderator
 5-Aug-2003 14:55
User is offline View Users Profile Print this message


Henock Gebreamlak

Posts: 3
Joined: 4-Aug-2003

Thank you! now I will try to follow what you suggested.

Henock
Report this to a Moderator Report this to a Moderator
 5-Aug-2003 14:56
User is offline View Users Profile Print this message


Henock Gebreamlak

Posts: 3
Joined: 4-Aug-2003



Edited: 5-Aug-2003 at 14:57 by Henock Gebreamlak
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic SYNERGY forum.
There are currently 0 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 15:34.
There are currently 0 guests browsing this forum, which makes a total of 0 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.