Delivered changeset not visible in other configurations of a component.
Hello Team,
Is there any way to identify to which stream the changeset belongs to?
We want the delivered changeset of one configuration to be visible in all the configurations of a component.?
Currently we are facing 402 error while delivering an already delivered changeset to another stream.
To create a dellivery session :
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dng_config="http://jazz.net/ns/rm/dng/config#" xmlns:oslc="http://open-services.net/ns/core#">
<dng_config:DeliverySession>
<dng_config:source rdf:resource="https://localhost:9443/rm/cm/changeset/_aJngsDFg"/>
<dng_config:target rdf:resource="https://localhost:9443/rm/cm/stream/_cZRfb2sVQ"/>
<oslc:serviceProvider rdf:resource="https://localhost:9443/rm/oslc_rm/_q986Y83YA/services.xml"/>
</dng_config:DeliverySession>
</rdf:RDF>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dng_config="http://jazz.net/ns/rm/dng/config#" xmlns:oslc="http://open-services.net/ns/core#">
<dng_config:DeliverySession>
<dng_config:source rdf:resource="https://localhost:9443/rm/cm/changeset/_aJngsDFg"/>
<dng_config:target rdf:resource="https://localhost:9443/rm/cm/stream/_cZRfb2sVQ"/>
<oslc:serviceProvider rdf:resource="https://localhost:9443/rm/oslc_rm/_q986Y83YA/services.xml"/>
</dng_config:DeliverySession>
</rdf:RDF>
source tag contains - changeset url
target tag contains. -- destination stream url.
Hint: This should work similar to deliver changes where we an option to select the change set that needs to be delivered.
Thanks and Regards,
Pavithra S
One answer
In DNG, you cannot directly deliver a completed/delivered change set to another stream in this way. A change set URI can only be specified as the source in a deliver session if it is open and the target is its parent stream.
When delivering changes from one stream to another (that is delivered changes from one stream to another) the API only currently allows the delivery of all delivered change sets that are in the source stream but not the target.
e.g. suppose we have two streams, Stream A and Stream B. Into Stream A we deliver CS1, CS2 and CS3. To get those change sets into Stream B you would need to create a delivery session where Stream A was the source and Stream B was the target, at this point there would be 3 deliverable change sets. In the UI you can pick to deliver only one of those change sets (although others might be automatically selected if there are dependencies between them), but at present the API does not currently support this.
I hope this answers your question, all be it perhaps unsatisfactorily.
Comments
In "Deliver Changes" functionality, we have an option where we can select express, standard or custom type. In Custom , we have an option where we can select the changesets that are available in the source stream (includes delivered changeset to the source stream) that has to be delivered to target stream.
Please do let me know whats the oslc api used here to view all the available changesets and how is the deliver changes working here?
Comments
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jan 23 '20, 10:39 a.m.This is only available for RTC/CCM.I do not know if the API or anything else provides this for DNG. However, from how it works for CCM, you can infer how complex and time/performance consuming this can be.
Pavithra Shivalingappa
Jan 23 '20, 11:39 p.m.Thomas Kirstätter
Jan 24 '20, 3:34 a.m.@Ralph Schoon: Thank you for your support. I think what we struggle with is in the context of the DNG properties distribution. When we import an update to the properties in a CHangeSet on one DNG stream, we want to deliver exactly this changeSet to all the other streams and nothing else. So, what seems to miss on our side is the knowledge about the API to distinctly deliver one specific changeSet from streamA to streamB
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Jan 24 '20, 6:10 a.m.