Source Control Getting Started
Are there any guidelines/best practices for getting started with RTC source control -- setting up components, loading code into RTC? Our project consists of five distinct elements, plus some common stuff -- build scripts & license files, for example. Some of this is Java and has Eclipse projects set up for it, but a bunch is not Java.
I've done some reading about local workspaces, repository workspaces and integration streams, but haven't found any "here's how you get started, step by step" stuff on setting this up. Chris |
10 answers
Based on the description of your project, I would recommend a component for each distinct element. Components help organize your projects in source control and eliminates loading unnecessary code. The common resources can go in its own component or maybe more if you want to separate the Java from non-Java resources.
So the first step would be creating your project area. Create any necessary streams and components. Create your workspace that flows to the stream. Other than that, perform your initial check-in any way you want after you've created the components. Any other things like team streams flowing to a main or integration stream can be set up as required. It's OK if you don't have streams for each team set up at the beginning. They can be created later and have the relevant components added. I think the key focus would be creating the necessary components to organize your versionables. Although, you may still move resources between components afterward. It's just best to have it set up first because the work for moving across components may be tedious and components cannot be deleted so they'll show up in component searches, which may be unsightly. Are there specific issues that you are unsure of how to proceed? Are there any guidelines/best practices for getting started with RTC source control -- setting up components, loading code into RTC? Our project consists of five distinct elements, plus some common stuff -- build scripts & license files, for example. Some of this is Java and has Eclipse projects set up for it, but a bunch is not Java. |
|
Yes. What is the process for loading the code into my local RTC workspace so that it can be checked into a repository workspace?
Chris |
|
Eclipse can import existing Java projects into its workspace. File -> Import -> Existing projects into workspace. Or go to Import -> File System for your non-Java resources.
Yes. What is the process for loading the code into my local RTC workspace so that it can be checked into a repository workspace? |
Eclipse can import existing Java projects into its workspace. File -> Import -> Existing projects into workspace. Or go to Import -> File System for your non-Java resources. Thanks tmok. I had the same question about my local RTC workspace. |
|
I created a general project in my Eclipse workspace and imported my source code to this. I can see it using the Resource perspective, but not with the Team Artifacts view.
I see how to create RTC components. I don't see how to associate these components with specific files in the Eclipse workspace or to check the files in to my repository workspace. Help appreciated! Chris |
Geoffrey Clemm (30.1k●3●30●35)
| answered Nov 09 '10, 12:38 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You would use the standard Eclipse command to do so.
In particular, Project Explorer or Package Explorer view, you would right click on the project you want to place under version control, and select "Team -> Share", and then select "Jazz" as your source control provider. The Eclipse folks decided that "Share" was a better verb than "version control" or "check-in" ... you'll have to take that terminology choice up with them (:-). Cheers, Geoff On 11/8/2010 5:38 PM, cbarlock wrote: I created a general project in my Eclipse workspace and imported my |
|
Ah! Makes sense. Similar to Team > CVS behavior. So obvious once someone tells you! :D
Chris |
Ah! Makes sense. Similar to Team > CVS behavior. So obvious once someone tells you! :D Hi Chris Something else for you to check - if you are using the Scrum template (and other templates do similar things), take a look at the work items that get created automatically when you create the project. These include a work item to import your source code, with instructions. These are all useful reminders of things you need to do when you start up a project. anthony |
|
OK, baby steps....I've played some with sharing files from the resource view. That seems to work OK. But, I have more questions, as RTC doesn't behave like the source control system we use (IBM's CMVC). CMVC concepts include "release," which ideally contains all the code that would ship as part of, well, a release and "components" which serve several purposes:
- Associate related files into groups - Allow assignment of work items to teams - Provide access control to files Looks to me like CMVC components are split into two RTC concepts -- work item categories and components. Fine; think I got it. From the first response in this thread, I thought that the files in a repository could be in multiple components. This would allow a user working on a subset of a project to load only those parts they need from a repository into a local workspace. If this is the case, not sure how it works. I used the Resource perspective to create a General project and import the file system that contains my source code. I then used the Team > Share project function to put this code into a repository workspace I created. I can't see how to divide this into multiple components. RTC seems to want to associate an entire project with one component. Once I share the project, even if I exclude all the files I don't want in a specific component, I can't share it again. Can I move specific files to different components or do that have to be created from separate Eclipse projects? (That would suck...) I totally understand that what I'm trying to do is map what I currently have to RTC concepts. I want to understand what to do so I have a chance at moving my team to use RTC for source control. We're using it for Agile management of stories & work items, but this leaves us split between two tools, which has its own pain points. Chris |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Nov 12 '10, 12:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In RTC, a given file or directory belongs to only one component, so you
cannot do the kind of overlapping components that exist in CMVC. In RTC, you can "move" a file from one component to another, but what that really does is create a new file (that is a copy of the original file), and then deletes the original file from the workspace. When you first "share" a file/file-tree/project is when you decide which component it will belong to (you are given a choice of which component to put it in, or to create a new component to put it in). WRT access control, RTC only provides read-access control at the component level. Cheers, Geoff On 11/10/2010 10:23 PM, cbarlock wrote: OK, baby steps....I've played some with sharing files from the |
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.