Lars Kruse created JENKINS-13574:
------------------------------------

             Summary: Support for ÚCM posted deliveries
                 Key: JENKINS-13574
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13574
             Project: Jenkins
          Issue Type: New Feature
          Components: clearcase-ucm
         Environment: ClearCase UCM MultiSite
            Reporter: Lars Kruse


In ClearCase MultiSite it's not possible to deliver directly to the parent 
(project integration) stream if it has different mastership the the development 
(current) stream.

Example: A developer is working in a USA replica, but the remainder og his team 
- and the project integration stream - is working in the Denmark replica - so 
he will have to integrate (deliver) to stream that is in Denmark.

For this scenario UCM supports the concept of a "posted deliver" - this is what 
happens in ClearCase:

- The developer makes a posted deliver - UCM create a special "posted deliver" 
object which is attached to the stream and then the mastership of the stream i 
automatically changed to Denmark.
- The information will have to transferred to Denmark replica using the regular 
shipping server export/import
- In Denmark nothing happens automatically: SOMEBODY will have to go to the USA 
developer's development stream (which is now mastered in Denmark) and issue a 
deliver -resume command.
- When the deliver process is either completed or cancelled, the mastership is 
automatically transferred back to USA again.

The feature request is, that the ClearCase UCM plugin becomes capable of 
polling for and automatically integratin with posted deliveries (on the 
receiving site) as if they were just another developer managed by the poll-self 
mode. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to