It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,788

question asked: Dec 10 '10, 3:36 p.m.
question was seen: 4,637 times
last updated: Dec 10 '10, 3:36 p.m.

Related questions

FAQ - How this Forum works

Component baseline replaced when stream is used in Build Def

0
Guowei Jim Hu (1.0k●8●103●53) | asked Dec 10 '10, 3:36 p.m.
One of our Dev. team recently found one day that the current component baseline of their main stream all of sudden has been replaced with an very old version and everone's workspace are now full of incoming /outgoing chnagset which have been done long time ago.

We fixed the issue by replace the wrong component baseline with the backup one created immediatedly before this happens.

Further investigating show that the cause is that:
1. one Build definition has been modified to set Build Workspace to the stream itself;

2. The stream's Flow Targets contains two workspaces with the same old component baseline which replaced the stream's current one;

From the build account xxxx's recent event list , we foun the statment:
xxxx replaced component 'LAMA' in stream 'mmi_main' with entry from workspace 'MMAC'

Workspace MMAC is the default/current workspace specified in the stream's Flow Target.

I guess one shouldn't user a Stream as Build Workspace in the first place. But the issue here is that it could happen and caused auto-baseline replacement which nobody wants.

Should this be considered as a bug?

4 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Dec 10 '10, 10:08 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I highly recommend that you never build directly against a stream, but
only against a workspace. This is but one of the anomalies that I have
seen occurring when you build against a stream. I've submitted a work
item that we just remove the ability to build against a stream.

But until then, I would submit this as a bug ... minimally, the
documentation should warn you about this.

Cheers,
Geoff

On 12/10/2010 3:38 PM, ghu wrote:
One of our Dev. team recently found one day that the current component
baseline of their main stream all of sudden has been replaced with an
very old version and everone's workspace are now full of incoming
/outgoing chnagset which have been done long time ago.

We fixed the issue by replace the wrong component baseline with the
backup one created immediatedly before this happens.

Further investigating show that the cause is that:
1. one Build definition has been modified to set Build Workspace to
the stream itself;

2. The stream's Flow Targets contains two workspaces with the same old
component baseline which replaced the stream's current one;

From the build account xxxx's recent event list , we foun the
statment:
xxxx replaced component 'LAMA' in stream 'mmi_main' with entry from
workspace 'MMAC'

Workspace MMAC is the default/current workspace specified in the
stream's Flow Target.

I guess one shouldn't user a Stream as Build Workspace in the first
place. But the issue here is that it could happen and caused
auto-baseline replacement which nobody wants.

Should this be considered as a bug?
0
permanent link
Guowei Jim Hu (1.0k●8●103●53) | answered Dec 13 '10, 7:41 a.m.
I highly recommend that you never build directly against a stream, but
only against a workspace. This is but one of the anomalies that I have
seen occurring when you build against a stream. I've submitted a work
item that we just remove the ability to build against a stream.

But until then, I would submit this as a bug ... minimally, the
documentation should warn you about this.

Cheers,
Geoff




Thanks, Geoff,
Rasied WI Defect 148029
0
permanent link
Nick Edgar (6.5k●7●11) | answered Dec 14 '10, 12:03 p.m.
JAZZ DEVELOPER
In 3.0 we now warn if a stream is selected. For details see comment 5 in the work item you filed.
0
permanent link
Guowei Jim Hu (1.0k●8●103●53) | answered Dec 15 '10, 7:38 a.m.
In 3.0 we now warn if a stream is selected. For details see comment 5 in the work item you filed.


Thanks, Nick.

Geoff has closed the WI but rasied a new one as we also found that there is no warning when one select a stream while walking through the wizard for configuring a personal build:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=148161.

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.