Multiple stream build
Hi all,
is it possible to have a build of multiple streams? Some like an integration build? I need this in order to handle common component shared between more stream. For example, I defined following streams with related components: stream_common: common_component stream_a: component_a stream_b: component_b In order to be built, both stream_a and stream_b require common_component source code. What I was thinking is to define the following three build definitions: build_stream_common: it only downloads stream_common code build_stream_a: download stream_a code + copy stream_common code just downloaded by build_stream_common and launch build build_stream_b: download stream_b code + copy stream_common code just downloaded by build_stream_common and launch build The problem is that, in this way, in the stream_a and stream_b build summary panel I am no more able to see all changes related to the common_component that have been included in the build just run. I saw that Jazz development project has weekly integration builds, are they multiple streams build? Thanks in advance for your help. Ciao, Tullio |
3 answers
You should set up a separate Repository Workspace for each build you want to run. In each Repository Workspace, include only the components you want built. It is ok to have components from multiple streams in the same Repository Workspace. If you use the built-in support for Jazz SCM, the build will get all of the change sets.
For example, to set up a build for component_a you would: 1. Create a new Repository Workspace "build_ws_a" from stream_a. Add the component common_component. (You can add components in the Workspace Editor). 2. Create a build definition that uses the Jazz SCM support. Specify build_ws_a as the Repository Workspace for the build. Martha Jazz Team Build Component |
|
Sorry, I misspoke in my last reply. You want to set the Flow Target for the Repository Workspaces, not add components.
So, the steps for setting up a build for component_a are: 1. Create a new Repository Workspace "build_ws_a" from stream_a. 2. Create a build definition that uses the Jazz SCM support. Specify build_ws_a as the Repository Workspace for the build. |
|
Hi all,
I would like to share with all of you the following e-mail from Martha. She answered to a my e-mail where I was asking the following question: "... If I well understood, the repository workspaces are a copy of personal workspace that each user creates on the server. These "personal" repository workspaces can be updated with changes delivered by users only if the owner of the repository explicitly accept the changes. They are different from streams which, if I well understood, are the production version of the product (they are always explicitly updated when a deliver is done). My question is the following one: ..."
I think this is a good info that could be useful to someone else. Ciao, Tullio |
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.