[
https://issues.jenkins-ci.org/browse/JENKINS-13964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Sorensen resolved JENKINS-13964.
-------------------------------------
Resolution: Fixed
Fixed in version 1.1.0
> Enhance the posted deliveries polling, so it can work 'as normal'
> -----------------------------------------------------------------
>
> Key: JENKINS-13964
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13964
> Project: Jenkins
> Issue Type: Improvement
> Components: clearcase-ucm
> Reporter: Leif Sorensen
> Assignee: Leif Sorensen
>
> The process for posted deliveries is a bit different from normal: on top of
> making the baseline, the developer must issue a Deliver Baseline command. A
> special "Posted deliver" object is then created, and the mastership of the
> development stream is transferred to the integration stream site. The plugin
> will detect the posted delivery, and resume and complete (or cancel) the
> delivery. As a result of this, the mastership of the stream will be
> transferred back to the origin. Notice: The ClearCase posted delivery process
> does not transfer the mastership of the baseline - for that reason the
> promotion level of the baseline cannot be changed, but is left as INITIAL.
> Tags can also not be updated.
> The plugin should be enhanced, so it can work in exactly the same way as in a
> single site setup: the developer just creates baselines, and everything else
> happens automatically.
--
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
