It's all about the answers!

Ask a question

Show deliver history and User that trigger every delivery for a given stream

Juan Pablo Soto (1825) | asked Mar 11 '15, 5:50 p.m.
 Hello Team! 
I've been dealing with this issue and being so close to my answer but in two days I wasn't able to get it there. For auditing purposes, I need to list "all the delivers with the responsable for each of them clear for all the environments (streams in my current model)". 
The big singularity that this installation has (CLM 4.0.1) is that they didn't use Work Items as part of their current process. It's something we want to fix ASAP, but we need to get green on an auditory before upgrading the tool and improve the process, so, we can't use any of the WI queries to get the deliver history, just scm commands. 

I've tried this (to summarize): 
lscm history -m 100 Component1 -r https://host:9443/ccm -u user (In order to see all
lscm compare -r local stream stream1 stream stream2 -r https://host:9443/ccm -u user
 lscm compare -r local stream Stream1 stream Stream2

And more that I didn't save the logs and nothing gives me the user that trigger the delivery action. 
So, in order to be even more clear, the output that I need (no matter if it's on one or on a sequence of commands) is: 

For a Stream, show me all the delivers that send a given changeset to that stream. Give me the user that trigger each deliver. 

(As on Recent Events for a project, but that works only for the last 100 and it's an RSS generated feed, nothing on the SCM or DW Database).

If you please can help me with how to get who triggers the deliver, I would be truly appreciated. 

Best Regards! 

Juan Pablo Soto
DevOps IT Specialist - IBM SSA

Accepted answer

permanent link
Rosa Naranjo (2.9k11623) | answered Mar 11 '15, 7:08 p.m.
I found this wiki link by using another forum post that sounded similar to what I think you are looking for.  Note that this functionality was added in RTC v5.0.1  for

Reference forum post:
Juan Pablo Soto selected this answer as the correct answer

Juan Pablo Soto commented Mar 13 '15, 9:45 a.m.

Hi Rosa! The only doubt that the client has on this is this. 

We are currently on 4.0.1. If we migrate to 5.0.2 (latest), are we able to see the history of this changes for the previous changesets? I mean, are we able to access to the deliverer (Added By) and the date of deliver (Date Added) for changesets older than the upgrade?

Thanks once again! 

Geoffrey Clemm commented Mar 13 '15, 11:59 p.m.

My understanding is that the upgrade from 4.0.1 to 5.0.2 will do its best to guess the added-by and date-added values for the pre-upgrade deliveries, but that those values will only be accurate for deliveries that occur after the upgrade has taken place.

Andrew Niefer commented May 26 '15, 2:39 p.m.

For any content created prior to the upgrade, the delivery information will be the same information that was previously available in the hover in the history view.

For changes that were directly delivered to the stream, this information will be as expected.    However, any changes that entered the stream via delivery of a baseline will have delivery information that reflect the original workspace or stream where the baseline was created.
For example: Alice delivers a change to StreamA and creates baselineA on that stream.  Then Bob delivers baselineA to StreamB, the history for StreamB will show Alice as the person who delivered the change, not Bob.  Starting in 5.0, the history will correctly show that Bob delivered the change to StreamB.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.