It's all about the answers!

Ask a question

Issue Accept and Delivey changes from Stream1 to Main_STream


Arun Kumar (1662017) | asked Feb 29 '12, 1:53 p.m.
Hi

I have set Main_Stream as flow target for Stream1 and stream2

but the Stream1 and stream2 modified the same file ( a.txt)

when the flow changes from Stream1 to Main_Stream

I can see changes in Outgong and Incoming, I am not able to accept or deliver..

"Cannot accept changes into a stream since they would create conflicts. Accept the changes into a repository workspace instead, resolve the conflicts, then deliver the merged chanes."

Please let me know the steps to resolve the above issue..

regards,

sriramk

7 answers



permanent link
Geoffrey Clemm (29.6k23035) | answered Mar 02 '12, 5:18 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I agree with David's post, but just to be make sure that there is no
misunderstanding, I'd modify the last sentence to say:

If a file is modified in Stream #1, then you will create a conflict
unless you ensure that the same file is modified in Stream #2 only after
the change from Stream #1 has been delivered to Stream #2.

Cheers,
Geoff


On 3/2/2012 12:50 PM, David Olsen wrote:
On 3/2/2012 7:24 AM, sriramak wrote:
yes, we have option for locking the file but multiple people wants
modify the common files from different reason from different Streams
( Target flowing to Main Streams)

WHen they are trying to deliver or accept the changes from Stream 1 to
Main stream or ( Stream2 to Main Stream) its giving conflicts..

so we have to change the flow target to accept on to the workspace and
we have to resolve the conflicts..

please let me know is there any way we can plan the streams to reduce
the conlicts.

No. If developers modify the same file in different streams and then
deliver those changes into a shared stream, there will be a conflict
because those changes need to be merged together.

If you need to avoid conflicts, then you need to stop modifying the same
file in different streams at about the same time. If a file is modified
in Stream #1, then the same file cannot be modified in Stream #2 until
the change from Stream #1 has been delivered to Stream #2.

permanent link
David Lafreniere (4.5k7) | answered Feb 29 '12, 4:58 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi

I have set Main_Stream as flow target for Stream1 and stream2

but the Stream1 and stream2 modified the same file ( a.txt)

when the flow changes from Stream1 to Main_Stream

I can see changes in Outgong and Incoming, I am not able to accept or deliver..

"Cannot accept changes into a stream since they would create conflicts. Accept the changes into a repository workspace instead, resolve the conflicts, then deliver the merged chanes."

Please let me know the steps to resolve the above issue..

regards,

sriramk


The error description gives clues as to what needs to be done. You can only resolve conflicts in a repository workspace. Therefore you must create a repository workspace flowing with Main_Stream first. Then you can change the flow target of that repository workspace over to Stream 1 and accept the change set that modified the same file a.txt. Now you can perform the merge in such a way that it is acceptable for Stream1 and deliver the merge back to Stream1. Repeat similar steps for Stream2.

Note: You could also do the reverse by creating a repository workspace first flowing with Stream1, and temporarily switch over to Main_Stream to accept the change set modifying a.txt, make the merge and deliver back to Stream1.

Also note that it is generally encouraged to deliver changes to streams through repository workspaces, and not from stream to stream. This will avoid issues such as this.

permanent link
Arun Kumar (1662017) | answered Mar 01 '12, 11:52 a.m.
Thanks david,

its very informative.. but we have One Main Stream target for 10 sub Streams..

but we can see two many conflicts on the stream to stream delivery or accept conflict..

yes, we cant resolve conflict on stream level... but how to reduce the conflict...

Regards,
sriramak


Hi

I have set Main_Stream as flow target for Stream1 and stream2

but the Stream1 and stream2 modified the same file ( a.txt)

when the flow changes from Stream1 to Main_Stream

I can see changes in Outgong and Incoming, I am not able to accept or deliver..

"Cannot accept changes into a stream since they would create conflicts. Accept the changes into a repository workspace instead, resolve the conflicts, then deliver the merged chanes."

Please let me know the steps to resolve the above issue..

regards,

sriramk


The error description gives clues as to what needs to be done. You can only resolve conflicts in a repository workspace. Therefore you must create a repository workspace flowing with Main_Stream first. Then you can change the flow target of that repository workspace over to Stream 1 and accept the change set that modified the same file a.txt. Now you can perform the merge in such a way that it is acceptable for Stream1 and deliver the merge back to Stream1. Repeat similar steps for Stream2.

Note: You could also do the reverse by creating a repository workspace first flowing with Stream1, and temporarily switch over to Main_Stream to accept the change set modifying a.txt, make the merge and deliver back to Stream1.

Also note that it is generally encouraged to deliver changes to streams through repository workspaces, and not from stream to stream. This will avoid issues such as this.

permanent link
Arun Kumar (1662017) | answered Mar 01 '12, 11:57 a.m.
Hi ,

How to restrict the folder or file deletion..

how to veriy who has deleted the folder and how we can find the folders history, who and when Created ?

regards,
sriram

permanent link
Geoffrey Clemm (29.6k23035) | answered Mar 01 '12, 11:50 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'm not sure what you mean by "two many conflicts on the stream to
stream delivery or accept conflict".

To reduce the conflicts, you could ask team members to lock that file in
One Main Stream before editing ... that would ensure that only one
person/stream at a time is modifying a given file.

Cheers,
Geoff

On 3/1/2012 11:54 AM, sriramak wrote:
Thanks david,

its very informative.. but we have One Main Stream target for 10 sub
Streams..

but we can see two many conflicts on the stream to stream delivery or
accept conflict..

yes, we cant resolve conflict on stream level... but how to reduce the
conflict...

Regards,
sriramak


daviddlwrote:
Hi

I have set Main_Stream as flow target for Stream1 and stream2

but the Stream1 and stream2 modified the same file ( a.txt)

when the flow changes from Stream1 to Main_Stream

I can see changes in Outgong and Incoming, I am not able to accept
or deliver..

"Cannot accept changes into a stream since they would create
conflicts. Accept the changes into a repository workspace instead,
resolve the conflicts, then deliver the merged chanes."

Please let me know the steps to resolve the above issue..

regards,

sriramk

The error description gives clues as to what needs to be done. You can
only resolve conflicts in a repository workspace. Therefore you must
create a repository workspace flowing with Main_Stream first. Then
you can change the flow target of that repository workspace over to
Stream 1 and accept the change set that modified the same file a.txt.
Now you can perform the merge in such a way that it is acceptable for
Stream1 and deliver the merge back to Stream1. Repeat similar steps
for Stream2.

Note: You could also do the reverse by creating a repository workspace
first flowing with Stream1, and temporarily switch over to Main_Stream
to accept the change set modifying a.txt, make the merge and deliver
back to Stream1.

Also note that it is generally encouraged to deliver changes to
streams through repository workspaces, and not from stream to stream.
This will avoid issues such as this.


permanent link
Arun Kumar (1662017) | answered Mar 02 '12, 10:23 a.m.
Hi Geoff,

THanks for the information..

We have 1 Main Stream is flow target for 10 Streams ( One Component).

when they are giving potential conflicts the changes are flowing from Stream to Main Stream.

yes, we have option for locking the file but multiple people wants modify the common files from different reason from different Streams ( Target flowing to Main Streams)

WHen they are trying to deliver or accept the changes from Stream 1 to Main stream or ( Stream2 to Main Stream) its giving conflicts..

so we have to change the flow target to accept on to the workspace and we have to resolve the conflicts..

please let me know is there any way we can plan the streams to reduce the conlicts.
regards
sriramsk

I'm not sure what you mean by "two many conflicts on the stream to
stream delivery or accept conflict".

To reduce the conflicts, you could ask team members to lock that file in
One Main Stream before editing ... that would ensure that only one
person/stream at a time is modifying a given file.

Cheers,
Geoff

On 3/1/2012 11:54 AM, sriramak wrote:
Thanks david,

its very informative.. but we have One Main Stream target for 10 sub
Streams..

but we can see two many conflicts on the stream to stream delivery or
accept conflict..

yes, we cant resolve conflict on stream level... but how to reduce the
conflict...

Regards,
sriramak


daviddlwrote:
Hi

I have set Main_Stream as flow target for Stream1 and stream2

but the Stream1 and stream2 modified the same file ( a.txt)

when the flow changes from Stream1 to Main_Stream

I can see changes in Outgong and Incoming, I am not able to accept
or deliver..

"Cannot accept changes into a stream since they would create
conflicts. Accept the changes into a repository workspace instead,
resolve the conflicts, then deliver the merged chanes."

Please let me know the steps to resolve the above issue..

regards,

sriramk

The error description gives clues as to what needs to be done. You can
only resolve conflicts in a repository workspace. Therefore you must
create a repository workspace flowing with Main_Stream first. Then
you can change the flow target of that repository workspace over to
Stream 1 and accept the change set that modified the same file a.txt.
Now you can perform the merge in such a way that it is acceptable for
Stream1 and deliver the merge back to Stream1. Repeat similar steps
for Stream2.

Note: You could also do the reverse by creating a repository workspace
first flowing with Stream1, and temporarily switch over to Main_Stream
to accept the change set modifying a.txt, make the merge and deliver
back to Stream1.

Also note that it is generally encouraged to deliver changes to
streams through repository workspaces, and not from stream to stream.
This will avoid issues such as this.


permanent link
David Olsen (5237) | answered Mar 02 '12, 12:50 p.m.
JAZZ DEVELOPER
On 3/2/2012 7:24 AM, sriramak wrote:
yes, we have option for locking the file but multiple people wants
modify the common files from different reason from different Streams
( Target flowing to Main Streams)

WHen they are trying to deliver or accept the changes from Stream 1 to
Main stream or ( Stream2 to Main Stream) its giving conflicts..

so we have to change the flow target to accept on to the workspace and
we have to resolve the conflicts..

please let me know is there any way we can plan the streams to reduce
the conlicts.

No. If developers modify the same file in different streams and then
deliver those changes into a shared stream, there will be a conflict
because those changes need to be merged together.

If you need to avoid conflicts, then you need to stop modifying the same
file in different streams at about the same time. If a file is modified
in Stream #1, then the same file cannot be modified in Stream #2 until
the change from Stream #1 has been delivered to Stream #2.

--
David Olsen | IBM Rational | Beaverton, Oregon

Your answer


Register or to post your answer.