Topic
  • 7 replies
  • Latest Post - ‏2013-10-28T20:31:29Z by ustad
SystemAdmin
SystemAdmin
47283 Posts

Pinned topic Deliver to alternate target - a serious curse

‏2004-01-18T17:34:52Z |
Hi All,

I seriously doubt the functionality offerred by Deliver to Alternate Target in ClearCase.

Think of a scenerio where two teams are supporting a product for two clients, each team working in a different UCM project. Project1 supports Client1 and Project2 supports Client2. Each project has a two level stream structure with the team working on development stream. Two cycles of testing will be done for each project, one at Dev stream level and another at the Integration stream level. Assume that 2 faults have been fixed in Dev stream of Project1. There need to go to the Client 2 as well. Hence deliveries (one for each fault) to the Dev stream of Project 2 were done. Now, when the Dev stream of Project1 is wanting to deliver the fault fix 2 to its Integration stream which has no conflicts with fault fix 1. This will error and show a conflict on fault fix 1. Neither of the faults can be independently delivered to the Integration stream in this case.

Same is the case with this kind of stream setup.

Int Stream

| - Dev Stream 1
| - Dev stream 2


Rational is not accepting this as a bug.

Any comments ?

thanks
Sunil
  • SystemAdmin
    SystemAdmin
    47283 Posts

    re:Deliver to alternate target - a serious curse

    ‏2004-01-19T12:51:05Z  

    Have
    you definitely tested that if you did not deliver the faults to
    Dev stream 2 then you can successfully deliver fault fix 2 into
    Int 1? If so then what is Rational's reason for not accepting it as a bug?
     
    Mark
    Williams

    -----Original Message-----
    From: Sunil Kuram
    mailto:sunil.kuram@caritor.com
    Sent: 18 January 2004
    13:35
    To: cciug@discussion.rational.com
    Subject: cciug
    Deliver to alternate target - a serious curse

    Hi All,

    I seriously doubt the functionality offerred by Deliver to Alternate Target
    in ClearCase.

    Think of a scenerio where two teams are supporting a product for two
    clients, each team working in a different UCM project. Project1 supports
    Client1 and Project2 supports Client2. Each project has a two level stream
    structure with the team working on development stream. Two cycles of testing
    will be done for each project, one at Dev stream level and another at the
    Integration stream level. Assume that 2 faults have been fixed in Dev stream
    of Project1. There need to go to the Client 2 as well. Hence deliveries (one
    for each fault) to the Dev stream of Project 2 were done. Now, when the Dev
    stream of Project1 is wanting to deliver the fault fix 2 to its Integration
    stream which has no conflicts with fault fix 1. This will error and show a
    conflict on fault fix 1. Neither of the faults can be independently delivered
    to the Integration stream in this case.

    Same is the case with this kind of stream setup.

    Int Stream
    |
    | - Dev Stream 1
    | - Dev stream 2

    Rational is not accepting this as a bug.

     













    <!--TEXT_SECTION-->

    **********************************************************************
    This email and any files transmitted with it are confidential and
    intended solely for the use of the individual or entity to whom they
    are addressed. If you have received this email in error please notify
    postmaster@radioscape.com.

    This footnote also confirms that this email message has been scanned
    for the presence of computer viruses known at the time of sending.

    www.radioscape.com
    *****************************************************************
  • SystemAdmin
    SystemAdmin
    47283 Posts

    re:Deliver to alternate target - a serious curse

    ‏2004-01-19T13:42:54Z  

    Have
    you definitely tested that if you did not deliver the faults to
    Dev stream 2 then you can successfully deliver fault fix 2 into
    Int 1? If so then what is Rational's reason for not accepting it as a bug?
     
    Mark
    Williams

    -----Original Message-----
    From: Sunil Kuram
    mailto:sunil.kuram@caritor.com
    Sent: 18 January 2004
    13:35
    To: cciug@discussion.rational.com
    Subject: cciug
    Deliver to alternate target - a serious curse

    Hi All,

    I seriously doubt the functionality offerred by Deliver to Alternate Target
    in ClearCase.

    Think of a scenerio where two teams are supporting a product for two
    clients, each team working in a different UCM project. Project1 supports
    Client1 and Project2 supports Client2. Each project has a two level stream
    structure with the team working on development stream. Two cycles of testing
    will be done for each project, one at Dev stream level and another at the
    Integration stream level. Assume that 2 faults have been fixed in Dev stream
    of Project1. There need to go to the Client 2 as well. Hence deliveries (one
    for each fault) to the Dev stream of Project 2 were done. Now, when the Dev
    stream of Project1 is wanting to deliver the fault fix 2 to its Integration
    stream which has no conflicts with fault fix 1. This will error and show a
    conflict on fault fix 1. Neither of the faults can be independently delivered
    to the Integration stream in this case.

    Same is the case with this kind of stream setup.

    Int Stream
    |
    | - Dev Stream 1
    | - Dev stream 2

    Rational is not accepting this as a bug.

     













    <!--TEXT_SECTION-->

    **********************************************************************
    This email and any files transmitted with it are confidential and
    intended solely for the use of the individual or entity to whom they
    are addressed. If you have received this email in error please notify
    postmaster@radioscape.com.

    This footnote also confirms that this email message has been scanned
    for the presence of computer viruses known at the time of sending.

    www.radioscape.com
    *****************************************************************
    Yes Mark,

    I have tested both the scenerios discussed in my message. We are running into scenerio 2 and Rational is not responding !!!??

    thanks
    Sunil

    Mark Williams wrote on Jan 19, 2004 - 03:51 AM ET
    >> 
    >> Have
    >> you definitely tested that if you did not deliver the faults to
    >> Dev stream 2 then you can successfully deliver fault fix 2 into
    >> Int 1? If so then what is Rational's reason for not accepting it as a bug?
    >> 
    >>  
    >> Mark
    >> Williams
    >> -----Original Message-----From: Sunil Kuram
    >> mailto:sunil.kuram@caritor.com Sent: 18 January 2004
    >> 13:35To: cciug@discussion.rational.comSubject: cciug
    >> Deliver to alternate target - a serious curse
    >> 
    >>  Hi All,
    >>  I seriously doubt the functionality offerred by Deliver to Alternate Target
    >>  in ClearCase.
    >>  Think of a scenerio where two teams are supporting a product for two
    >>  clients, each team working in a different UCM project. Project1 supports
    >>  Client1 and Project2 supports Client2. Each project has a two level stream
    >>  structure with the team working on development stream. Two cycles of testing
    >>  will be done for each project, one at Dev stream level and another at the
    >>  Integration stream level. Assume that 2 faults have been fixed in Dev stream
    >>  of Project1. There need to go to the Client 2 as well. Hence deliveries (one
    >>  for each fault) to the Dev stream of Project 2 were done. Now, when the Dev
    >>  stream of Project1 is wanting to deliver the fault fix 2 to its Integration
    >>  stream which has no conflicts with fault fix 1. This will error and show a
    >>  conflict on fault fix 1. Neither of the faults can be independently delivered
    >>  to the Integration stream in this case.
    >>  Same is the case with this kind of stream setup.
    >>  Int Stream|| - Dev Stream 1| - Dev stream 2
    >>  Rational is not accepting this as a bug.
    >>   
    >> 
    >> **********************************************************************
    >> This email and any files transmitted with it are confidential and
    >> intended solely for the use of the individual or entity to whom they
    >> are addressed. If you have received this email in error please notify
    >> postmaster@radioscape.com.
    >> 
    >> This footnote also confirms that this email message has been scanned
    >> for the presence of computer viruses known at the time of sending.
    >> 
    >> www.radioscape.com
    >> *****************************************************************
  • SystemAdmin
    SystemAdmin
    47283 Posts

    re: Deliver to alternate target - a serious curse

    ‏2004-01-19T15:25:14Z  
    Hi Sunil,

    I'd like to comment but I must admit I have troubles understanding your scenario. Maybe you can provide a small sketch?

    Could you explain more on the error you are getting? Maybe it has to do with the deliver-baseline on the dev-stream which is implicitly made with each delivery. Why don't you deliver fix 1 also to int-1, if it was good enough to be delivered to int-2? Your projects have to cooperate to do proper scheduling of the fixes; if they delivered fix-2 prior to fix-1 there would've been no problem, I think.

    If bugfix/common release planning is a problem, you would need a stream for each fix or feature; and I also would think about a project for the common development, in addition to the client-1 and client-2 projects. Wouldn't solve your current problem, but I would think it provided more structure.

    Best Regards, Walter

    Sunil Kuram wrote on Jan 18, 2004 - 08:34 AM ET
    >> 
    >> Think of a scenerio where two teams are supporting a product for two clients, each team working in a different UCM project. Project1 supports Client1 and Project2 supports Client2. Each project has a two level stream structure with the team working on development stream. Two cycles of testing will be done for each project, one at Dev stream level and another at the Integration stream level. Assume that 2 faults have been fixed in Dev stream of Project1. There need to go to the Client 2 as well. Hence deliveries (one for each fault) to the Dev stream of Project 2 were done. Now, when the Dev stream of Project1 is wanting to deliver the fault fix 2 to its Integration stream which has no conflicts with fault fix 1. This will error and show a conflict on fault fix 1. Neither of the faults can be independently delivered to the Integration stream in this case.
    >> 
    >> Same is the case with this kind of stream setup.
    >> 
    >> Int Stream
    >> |
    >> | - Dev Stream 1
    >> | - Dev stream 2
    >> 
  • SystemAdmin
    SystemAdmin
    47283 Posts

    Re: re: Deliver to alternate target - a serious curse

    ‏2005-12-19T10:56:31Z  
    Hi Sunil,

    I'd like to comment but I must admit I have troubles understanding your scenario. Maybe you can provide a small sketch?

    Could you explain more on the error you are getting? Maybe it has to do with the deliver-baseline on the dev-stream which is implicitly made with each delivery. Why don't you deliver fix 1 also to int-1, if it was good enough to be delivered to int-2? Your projects have to cooperate to do proper scheduling of the fixes; if they delivered fix-2 prior to fix-1 there would've been no problem, I think.

    If bugfix/common release planning is a problem, you would need a stream for each fix or feature; and I also would think about a project for the common development, in addition to the client-1 and client-2 projects. Wouldn't solve your current problem, but I would think it provided more structure.

    Best Regards, Walter

    Sunil Kuram wrote on Jan 18, 2004 - 08:34 AM ET
    >> 
    >> Think of a scenerio where two teams are supporting a product for two clients, each team working in a different UCM project. Project1 supports Client1 and Project2 supports Client2. Each project has a two level stream structure with the team working on development stream. Two cycles of testing will be done for each project, one at Dev stream level and another at the Integration stream level. Assume that 2 faults have been fixed in Dev stream of Project1. There need to go to the Client 2 as well. Hence deliveries (one for each fault) to the Dev stream of Project 2 were done. Now, when the Dev stream of Project1 is wanting to deliver the fault fix 2 to its Integration stream which has no conflicts with fault fix 1. This will error and show a conflict on fault fix 1. Neither of the faults can be independently delivered to the Integration stream in this case.
    >> 
    >> Same is the case with this kind of stream setup.
    >> 
    >> Int Stream
    >> |
    >> | - Dev Stream 1
    >> | - Dev stream 2
    >> 

    Hi,

    As part of a deliver from any stream to any other a baseline is applied to the delivering stream. It is then that baseline that is actually delivered under the covers. When delivering a subset of activities on a stream you cannot pick and choose from the activities before the latest baseline. You can take all of them or none of them.

    In the scenario you have described this is expected, although perhaps not welcome, behaviour.

    Jim
  • ustad
    ustad
    3 Posts

    Re: Deliver to alternate target - a serious curse

    ‏2013-10-24T18:23:51Z  

    Sunil,

    we are kind of finding ourselves in the same boat. Did you ever get this scenerio resolved or any work-around?

     

    Thanks.

    Namit

  • Dave-Robinson
    Dave-Robinson
    116 Posts

    Re: Deliver to alternate target - a serious curse

    ‏2013-10-28T00:23:56Z  
    • ustad
    • ‏2013-10-24T18:23:51Z

    Sunil,

    we are kind of finding ourselves in the same boat. Did you ever get this scenerio resolved or any work-around?

     

    Thanks.

    Namit

    Hello Namit,

    There has been some modification to ClearCase since 2004 to minimize the "dependency" between activities.

    For a more specific response, I would invite you to start a new thread giving some more detail to your own situation.

    David

  • ustad
    ustad
    3 Posts

    Re: Deliver to alternate target - a serious curse

    ‏2013-10-28T20:31:29Z  

    Hello Namit,

    There has been some modification to ClearCase since 2004 to minimize the "dependency" between activities.

    For a more specific response, I would invite you to start a new thread giving some more detail to your own situation.

    David

    Yes you are right Dave. I found that I had to add a system variable named REVERT_CMBU00060301 with value as TRUE in order to get it resolved. It works as expected now. Thanks.