How to avoid work items to be mixed between two build definitions that use different workspaces but common stream?
I have a code stream "Main Development Stream" which has components say:-
Main Build Definition needs to build code in component 1 and component 2 whereas Common Build Definition needs code only from common component. Below are my expectations:-
Please note I want to make the two builds completely independent of each other, and should not mix work items . I tried the 'Components to exclude' option to exclude components in the build definitions, but it did not seem to have any effect. I also tried creating "Common Build Definition Workspace" by including just the common component, but the RTC refreshes and accepts other components automatically when we request a new build. Any pointers to achieve what I want, would be appreciated! Thanks! |
Accepted answer
Open "Common Build Definition Workspace" in an editor. Remove Component 1 and Component 2 from the list of components. In the Flow Targets section near the bottom of the editor, click on the flow target for the stream. Click the Edit button. Select "Flow only components checked below." Select only Common Component. Click OK to close the dialog and click Save to save the changes to the repository workspace.
Repeat these steps for "Main Build Definition Workspace," but remove Common Component and flow with Component 1 and Component 2.
Editing the flow target in this way will keep RTC from adding the components back into the workspace when you run a build.
-- David Olsen, IBM Rational, Jazz Process Team
Mangirish Wagle selected this answer as the correct answer
|
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.