It's all about the answers!

Ask a question

What is the best way to create an RTC component?


Sreedhara thirthahalli (591215) | asked Aug 18 '14, 12:09 a.m.
edited Aug 20 '14, 12:39 a.m. by Geoffrey Clemm (30.0k23035)

Hi

We were using clearcase UCM and recently we moved to RTC 5.0 , and in my old clercase ucm setup development team is having small small code of different different projects say approximately 80 projects

My setup was one PVOB and One Single VOB and under that I use to create a component using

 "COMPONENT INSIDE THE VOB" (selecting base vob.)

and I will create a New Project under PVOB and associate the newly  created component and created a Intial baseline.  and after that using integration view and selecting the correct component I will import the their particular project source code (data) to COMPONENT. and developers will create a child stream and deliver their work to newly created project integration stream.

My setup will be

One Single PVOB and one single VOB under that many projects  will be there and each project will have their own components

The reason behind doing the above setup is if any body asks what is the new release for that particular project, that time just go to Project integration stream and get the latest baseline.

.

My query is :-  How can I do the same setup in RTC, Mainly I am looking for if any body asks what is your latest baseline of that Project? or what is the latest release number?

1) Do I need to create a 80 different projects  or

2) Once I create a Main a project, default streams and default component will create under that do I need to create a New components for that particular project source codes and Import the source code to the newly created components?

3) If I go with the Number 2 option creating a new component, If some one asks what is your latest baseline of that project I can't able to tell right.


Comments
Geoffrey Clemm commented Aug 20 '14, 12:41 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Note that it is important to title your question with an actual question (not just a phrase like "RTC Project").   I've edited the title to turn it into a question ... please edit further if that isn't the question you meant to ask.

One answer



permanent link
Geoffrey Clemm (30.0k23035) | answered Aug 19 '14, 12:56 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The main difference between RTC and UCM-ClearCase in this regard is that what UCM-ClearCase calls a "composite baseline", RTC calls a "snapshot".
So just as in ClearCase UCM, in RTC, you would create a "project integration stream" to capture the evolving state of your components for that project (including the addition and removal of components to/from that project).  When that stream has reached a state you want to remember, you would create a snapshot of that stream.  So:
(1) You would create a single project integration stream (RTC does not have an object called a "project").
(2) Just as with UCM ClearCase, you can either add components from other projects to this project integration stream, or if this is the first time this component is used in any stream, you could create a new component to add to this project integration stream.
(3) I'm not quite sure what is being asked here ... perhaps the comments above have covered this topic?

Comments
Sreedhara thirthahalli commented Aug 19 '14, 4:50 a.m.

 Hi Geoffrey

thanks for the reply But I am not looking for "COMPOSITE BASELINES"

1) What is the Best way to create a Components?
By using "my repository work space" ---> New---> Component
or
in the stream level by click NEW

Why I am asking is

If I create a component using NEW Compoent will be created as project scoped and at the same time new stream also will be created is it the correct way to create a New component

or 
under repository workspace---> Right click---> component 
My intension is Importing the code to the components.




Geoffrey Clemm commented Aug 20 '14, 12:55 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Either way to create a component is fine ... the only difference is that when you create a component in a stream, it is initialized to be owned by the owner of that stream, while when you create a component in a workspace, it is initialized to be owned by you.   But since you can easily change the ownership of the component, and you can easily add/remove an existing component to/from a stream/workspace, it doesn't matter where/how you create the component.


Sreedhara thirthahalli commented Aug 20 '14, 8:00 a.m.

Hi Geoffry

Thanks for the detailed answer for the owner ship of Components.

One more query:-

I have 10 different different projects source code (data)

Do I need to create a separate stream and separate component for each project ?

(I need to import source codes to that particular component)

What is the best way to have it? or I can put Best way to organize it


Sreedhara thirthahalli commented Aug 20 '14, 8:12 a.m.

Hi Geffory

Some more on the above queries...

the above Project I mentioned was (source code data) of that particular team or project

in my UCM I will be creating a Separate stream and separate component for each team (projects data or projects source code) and after their modification they will deliver to their project integration stream.

Coming to RTC:-

How can I go for that?

Can I go with separate stream and separate component?

and as a admin import the source code to that particular component so their will not be any confusion after their work done and they will deliver it to default target stream.

Please advice here about seperate stream and sparate component


Geoffrey Clemm commented Aug 21 '14, 7:12 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

One RTC stream for importing all projects should be sufficient (no reason I can think of for having a separate stream per component).
WRT how many projects to store in a given component:
- The primary semantics of a component is that it defines the scope of a "baseline".  So if two projects depend on each other to the extent that you'd never create a baseline of one without also creating an associated baseline of the other, it would make sense to put the two projects in the same RTC component.
- Another important characteristic of an RTC component is that a given change set belongs to an RTC component.  So if you decide you need to relocate some files from one component to another, it is hard to apply a change set from the original component to the new component.   This means that if it is likely that you will want to refactor some files between two projects, it is best to have them loaded into the same RTC component.


Your answer


Register or to post your answer.