[p4] Drawing branch-diagrams

[James M Nguyen]

I had contacted Perforce Technical Support in the past regarding a BRANCH level revision graph but was told such feature did not exist (at the time). The FILE revision graph can be used as a workaround but can get really messy. If there is one consistent file  residing under each branch or simply a dummy file (i.e. readme.txt), you can use the "p4 filelog //<path>/readme.txt" to gather all its integrated information, manipulate the data, generate a branch map, and display it.

Here at my company, someone before my time had developed it using PHP which can be viewed and refreshed via a web interface. Although more complicated, it works beautifully.

Regards,
~James Nguyen




________________________________
From: Felix Drueke <fdrueke at orga-systems.com>
To: perforce-user at perforce.com; sjamison at ciena.com
Sent: Friday, October 24, 2008 6:38:07 AM
Subject: Re: [p4] Drawing branch-diagrams

Hi Shawn,

thanks for the hint.

Yes - I know the revision-graph and it's a help, but what we want to do
is more like planning future branches and integrations.
The revision graph can only show the history.

Felix




perforce-user-bounces at perforce.com wrote, on 24/10/08 02:44 PM:
> P4V's revision graph will help a lot! 
> 
> 
> -Shawn Jamison>
> Ciena Corp.
> Perforce Admin
> 
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Felix Drueke
> Sent: Friday, October 24, 2008 8:33 AM
> To: perforce-user at perforce.com
> Subject: [p4] Drawing branch-diagrams
> 
> Hi,
> 
> we have a whole jungle branches for the development of new features of
> our various software-products.
> Each of these branches has a purpose and a planned end-date (which often
> changes) and has a designated target-branch (usually a so-called
> main-line) to that its changes will be integrated.
> 
> In order to bring a bit light into the jungle I started to draw diagrams
> which show what branches exist, what integrations have to be performed
> (from where to
> where) and what the planned end-dates for each branch are.
> I'm doing that with MS-Visio which hurts, because I spent more and more
> time updating the diagrams and drawing new lines (for branches or
> integrations between the branches).
> 
> Does anyone do something similar? What tool(s) can you recommend?
> 
> Thanks for any hints,
> Felix
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user