It's all about the answers!

Ask a question

Jazz Article: Using the SCM Command Line Interface in builds

William Byrne (5545) | asked Mar 20 '10, 12:40 a.m.
I have questions regarding the Jazz article: Using the SCM Command Line Interface in builds

I have the following ws/stream configuration:

  My WS ---* Team Stream (components) *----* Build WS ---* Integration Stream

Flow direction is indicated by the asterisks. (I needed to use asterisks instead of arrowheads because the forum software mangled the text when I used gators and dashes)

My WS changes are delivered to Team Stream (components) which belongs to the project hosting the components used in the build. Build WS is the designated workspace for the build. I'm promoting built-proven snapshots to Integration Stream.

The build process for Build WS produces artifacts that I'd like to store back into Team Stream (components). I'm getting an error, however, during the build: Component MyComponent is accepting changes from multiple flow targets

where MyComponent is hosted in the Team Stream (components) project hierarchy.

I noticed that Recipe #1 in the article talks about flowing artifacts back into components, and I'm wondering why I'm getting errors. Do I need to programmatically disconnect My WS from Team Stream (components), or lock something to avert the exceptions?

I also tried routing the build artifacts from Build WS through My WS, but the multiple flow targets exception was still generated.

3 answers

permanent link
Evan Hughes (2.4k1318) | answered Mar 24 '10, 12:06 p.m.
The following is incorrect. Please see my next post.

I believe that you should be able to specify the a default flow target for your build workspace. With that, the build will know which stream to accept from.

(Give this a shot, I'm checking around here to see if anyone else has a more authoritative answer)


permanent link
Evan Hughes (2.4k1318) | answered Mar 24 '10, 12:13 p.m.
You're getting the complaint because the build workspace has flows with multiple streams that contain the same component. It doesn't know which version to accept so it's producing that error.

For your situation, I believe you can remove the flow to your Integration Stream, and then explicitly deliver your changes using the --target and --source options.


permanent link
Nick Edgar (6.5k711) | answered Mar 31 '10, 4:37 p.m.
Yes, Build pulls changes into the build workspace from all flow targets.
You can either remove extra flow targets, or if you really do want to bring in changes from multiple targets, you can edit the build workspace's flow targets to have scoped flows, so that it pulls some components from one target and others from another target. They should be non-overlapping.

> the forum software mangled the text when I used gators and dashes
Try unchecking 'Disable HTML in this post'.

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.