All the components are loaded to local during build request
Hi All,
One of our customers are using CLM 3.0.1. They are making their build by using Rational Build Engine. There are 3 streams and there are some components under those streams. We created one single builduser which will handle all the builds. And that user has one Repository workspace for each component like: Component A WorkSpace -> Component A Component B WorkSpace -> Component B There are also different build definition for each component. And all those build definitions are connected to the specific repository workspace. Till now everything was working fine. But they reported me that whenever they send a build request for Component A, the other components are also loaded to the loca file systeml. As far as I know only the specific component should be loaded to the local file system? Am I right? I couldn't see what am I missing? Caould help me with that? |
7 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 21 '11, 5:58 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I assume that in the Jazz Source Control page, you have the "Accept
latest changes before loading" box checked? If so, in order to prevent it from accepting all the components in the stream, you need to go into your Workspace editor, and in the Flow Targets section, select the target stream, and click on the Edit button. The select the "flow only components selected below" check-box, and select the single component you want in this workspace. Or have you already done that? Cheers, Geoff On 7/21/2011 2:53 PM, canberk wrote: After your answer I re-checked this "Excluded components" |
Hi Canberk,
Here is one thing that you can check. In the Build Definition, there is a tab named "Jazz Source Control". Click on that and on that page there is a section where you can "exclude" specific components. You can check to see if the appropriate component is selected there or not. For example, if you "exclude" component B in the Build Definition used for building component A, that will prevent component B from being loaded during the build. Hi All, |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 21 '11, 2:20 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
By default, all components in the workspace are loaded.
In the Jazz Source Control page of your build definition, there is a section called Load Options, you can specify what components to exclude from the load, as well as what subset of the directories to include in the load. By the way, I'd recommend each of your build definitions to have its own build workspace, to keep them from stepping on each other. Cheers, Geoff On 7/21/2011 10:53 AM, canberk wrote: Hi All, |
|
@wmansur: I already checked that. When I press the Excluded Component section I only see the component that's been bind to the workspace. I only see the Component A in the Workspace A. I cant see Component B. If I saw it, it would be not logical cause only Component A is added to my workspace.
@gmclemm: have separate workspace for my component. I have 20 component and I have 20 workspace for build user. And also have 20 build definition. If all the components are loaded to my local, why I create a repository for space for every component. And if so whenever I add a new component to my stream I have to edit the Load Configuration. It seems not logical to me. |
|
After your answer I re-checked this "Excluded components" and I saw that all the components were listed there. Then I checked my repository workspace and I saw that Component B was added to my Component A's Repository Workspace. And component A was added to Component B's repository workspace.
I removed the component B from Component A's repository workspace. And requested another build request. During the fetching phase component B was added again to component A's workspace. And in the first phase, as I have one component in the workspace, I can't exlude the second one from loaded. That's also not logical to me. I created this repository workspaces for specific component. |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 21 '11, 5:53 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I misinterpreted your original post. When you said:
"There are also different build definition for each component. And all those build definitions are connected to the specific repository workspace." I interpreted that as meaning that "each component has a set of different build definitions and each of those build definitions is connected to the repository workspace for that component". It is now clear that this should have been interpreted as saying "each component has its own build definition" (which is fine, since each build definition is associated with exactly one repository workspace). Cheers, Geoff On 7/21/2011 2:53 PM, canberk wrote: @gmclemm: have separate workspace for my component. I have 20 |
|
That's exactly what I have been looking for.
Thank you very much :) |
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.