5 messages in com.perforce.perforce-user[p4] reporting changelists not integr...| From | Sent On | Attachments |
|---|---|---|
| Robert Love | 13 Mar 2003 09:15 | |
| Jeremy Russell | 13 Mar 2003 09:41 | |
| Rus Maxham | 13 Mar 2003 13:06 | |
| Paul C. Pharr | 13 Mar 2003 14:28 | |
| Brian Colfer | 19 Mar 2003 15:23 |
| Subject: | [p4] reporting changelists not integrated into branch |
|---|---|
| From: | Brian Colfer (bcol...@get.topica.com) |
| Date: | 03/19/2003 03:23:47 PM |
| List: | com.perforce.perforce-user |
Have you thought about using p4 -G integrated //depot/project/branch/... or p4 -ztag ntegrated //depot/project/branch/... | grep "... change " | uniq | cut -f3 -d" " > changelists.txt for i in `cat changelists.txt`; do p4 describe -ds $i >> MergeSummary.txt ; done
-----Original Message----- From: perf...@perforce.com [mailto:perforce-user-admin at perforce.com] On Behalf Of Rus Maxham Sent: Thursday, March 13, 2003 13:07 To: 'Robert Love'; perforce-user at perforce.com Subject: RE: [p4] reporting changelists not integrated into branch
I've written a script to do this. What I wrote the script to do is to collect all of the comments on changelists submitted on my branch that would be integrated when I integrate the branch, so I can see all of what I did, and optionally use that as the comment for the integration.
It uses 'p4 integ -b {branchname} -n' to preview what would be integrated. The output is parsed to see what file revisions would be integrated, then cross references each and every file revision to a changelist. The resulting changelist-list is used to gather all of the comments for the final report.
In pseudocode:
p4 integ -b branch -r -n > filerevlist
foreach filerev p4 changes filerev >> changes
{prune duplicate changelists}
foreach change p4 describe change >> report
One trick I had to do is to translate the filerevspec from p4 integ into a rev range for use with p4 changes.
I actually have implemented this as an Active Server Page with embedded PerlScript, so my users can get at this tool from the web. If you'd like it, I can forward it on to you.
rus
-----Original Message----- From: Robert Love [mailto:RobertL at csl.com] Sent: Thursday, March 13, 2003 9:16 AM To: perforce-user at perforce.com Subject: [p4] reporting changelists not integrated into branch
I have two branches; my main development branch and from that I have a release branch. I'd like to be to produce a report which lists all the changelists which have been submitted to the main branch but have yet to be integrated into the release branch. Specifying any ranges to constrain the report would be a bonus, but not necessary. I've read the help on reports but can't really see how this would be possible. I could well understand if it wasn't since what would happen if the latest version of a single file had been integrated to the release branch. That file could be part of many unintegrated changelists so would mean that some changelists have been partially integrated. However, this is not so much of a problem for us as we try at all times to only integrate specific, individual, changelists to the release branch.
Perhaps some scripting gurus know of a way to produce such a report.
Many thanks for any help Rob