Jazz RTC Version control system Code Tagging/Branching
Hi All,
I am a new bee to RTC. I would like to create a branch (which i used in other Version systems like CVS) for my project in RTC version control system. so as to i can have two separate development version one for Production environment and other for Enhancement part. How can we achieve it using RTC. Regards, Phanindra |
Accepted answer
I dont' t know, how to realize making a "branch" in RTC. Hi Assuming you already have a stream called Production Stream - try this: Go to your project in your IDE make sure you are looking in the Team Artifacts view. Expand the project so you can see the Source Control folder. Right button and select New->Stream. Call it Enhancement Stream. A wizard will allow you to select the components you want from your Production or any other stream. You now have something similar to a branch. To start working on code, go to your project in your IDE. Right button on My Repository Workspaces and select New->Repository Workspace. Using the wizard, select Flow with a Stream and select your Enhancement Stream. You can select Finish at this point, or go to the other screens to select specific options. By default, it will create a new repository workspace called <name> Workspace, and load it on your local machine. Later on - when you want to push your changes back to the Production Stream, right button on your repository workspace and select Change Flow Target and select your production stream. You can then deliver all your changes to the Production Stream. RTC does have some different concepts, so definitely look at some of the introductory articles to help yourself get familiar with the terms and concepts. It is very easy and powerful once you get the basic ideas like Stream, Workspace, and Components. Does that help? anthony Ralph Schoon selected this answer as the correct answer
|
8 other answers
phani4jazz wrote:
I would like to create a branch (which Create a new stream. To effectively branch you source, just deliver a change set to one stream but not the other. RTC takes care of all the branching under the covers. You never have to worry about explicitly branching something or merging it later. You just move change sets around between streams. |
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 02 '10, 7:10 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'd suggest looking at the article "Multiple Stream Development":
http://jazz.net/library/article/40 Cheers, Geoff On 9/2/2010 2:37 PM, gbsills wrote: .. Create a new stream. To effectively branch you source, just deliver a change set to one stream but not the other. RTC takes care of all the branching under the covers. You never have to worry about explicitly branching something or merging it later. You just move change sets around between streams. This sounds great but a more detailed description would be helpful. Could you point us to one? Comments I've read the article about Multi-Stream Developement,
|
...
Create a new stream. To effectively branch you source, just deliver a change set to one stream but not the other. RTC takes care of all the branching under the covers. You never have to worry about explicitly branching something or merging it later. You just move change sets around between streams. This sounds great but a more detailed description would be helpful. Could you point us to one? |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Oct 28 '10, 12:17 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In RTC, a "branch" is represented by an RTC stream.
Not sure what you mean by "made a new baseline from the component of one of the workspaces as Branch". A baseline is an immutable configuration, not a branch. In RTC, you can initialize a stream from a baseline ... is that perhaps what you meant? Cheers, Geoff On 10/27/2010 6:38 AM, MartinI88 wrote: I've read the article about Multi-Stream Developement, |
I dont' t know, how to realize making a "branch" in RTC.
It's not exactly described. Can you please give me some information, how to make a new stream as branch and which I had to use as sourcereference (component, baseline...) |
|
yes, thats the missing pieces of knowledge.
Thank you for your detailed answer!! |
Just wondering any of you are using the Rational collaborative application life cycle management in a software development environment (i.e RRC, RTC and RQM in one setup). If so please let us know how you find this jazz development environment for about 20 developers. What is the recommended source control system?
How easy is it to migrate large number of programs with multiple branches to Jazz source control system ? Thanks, Thushara. |
Just wondering any of you are using the Rational collaborative application life cycle management in a software development environment (i.e RRC, RTC and RQM in one setup). If so please let us know how you find this jazz development environment for about 20 developers. What is the recommended source control system? As far as source control goes, use RTC for your source control, it has it built in through the IDE. If you want it for more than 10 developers then you will have to buy the product from IBM. As far as migrating your source data over I'm not sure how easy it is to do, I know parts of IBM will do it for you (if you pay them obviously) such as the Platform Technology Center based in Hursley in the UK. Hope this helps. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.