It's all about the answers!

Ask a question

Sharing components between different project areas

Norman Dignard (356690170) | asked May 21 '15, 8:09 a.m.

We have 2 seperate projects each with its stream and set of components.  They now want to use/share the same component from PA1 stream to PA2 stream.   Changes are only done in the PA1 stream and they want these changes to be seen in the PA2 stream .   They have added the component to the PA2 stream but now they see that changes delivered to the PA1 stream  do not automatically get seen on PA2.

It appears that you either have to manually deliver the changes to both stream or in the PA2 stream replace the component to get the latest changes visible. At least this is the behavior we noted where no snapshot was made.

To clarify  In PA1 the component has 2 changesets since the "initial" baseline.  They added the component to PA2 and in that PA the component also showed 2 changesets. Several additional changes where then made in PA1 and the component now showed several changeset since "initial" but in PA2 it still only showed the original 2 changesets.  They then had to replace the component in PA 2 for it to see the same changes as in PA1.

Is there a better way of "sharing" componets between PAs?  It appears that you have to deliver the changeset to each PA stream or create snapshots and replace the compoenet with a later snapshot.  



Accepted answer

permanent link
Martha (Ruby) Andrews (3.0k44351) | answered May 21 '15, 2:44 p.m.
I do not know of a way to "share" components between stream. However, you can flow baselines for the components between streams instead of replacing.
Set up a repository workspace from PA1 stream.
Load the workspace in you local client
Accept whatever changes are in PA1 stream
Create a baseline
Change the flow target for the component to PA2 stream
Deliver baseline.

This is a manual process that can be done on a regular schedule to "publish" the changes from one stream into another.

Martha (Ruby) Andrews
Jazz Foundation L3 Development Team Lead
Norman Dignard selected this answer as the correct answer

One other answer

permanent link
Geoffrey Clemm (30.1k33035) | answered May 21 '15, 6:22 p.m.
This is not currently supported, but has been requested in Allow a stream to "share" a component from another stream. (127541)
The closest you can currently come is to implement a post-deliver action, that automates this deliver.
Somewhat simpler to implement would be a build job that runs ever X hours, that performs this deliver.
Note that if there are no conflicts, you can deliver directly from the first stream to the other stream (no need to perform the deliver via a workspace).

Norman Dignard commented May 22 '15, 7:35 a.m.

Thanks for the info. Its nice to know its been in the backlog forĀ above 5years with no resolution in sight.

Your answer

Register or to post 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.