[p4] How to specify a release for build team?

[Helck, Christopher]

Hi,

I'm curious how people fully specify a release in Perforce. Let me
explain. Typically when our development group is ready to make a release
of a product (Product-A say) they create a release branch, tag the
files, and give the build team the label name. The build team syncs to
the label, looks for a file called "certbuild" and executes it (this in
turn kicks off a maven or ant build).

The problem is that some projects have complex views. Before a release a
developer often logs onto the build machine and tweaks a custom view.
This is bad for all sorts of reasons including that previous builds
can't be reproduced.

I can think of three solutions:

1. Require all builds to use a default view.
2. Cut and past the view contents, send it to the build team, and have
them modify the view.
3. Developers create customer views that match the label name. So if the
label is product-a-2.4.5 then there will be a view with the same name.

Any other ideas or suggestions?

Regards,
C. Helck


 
Thank you for being part of it.
 
The information contained in this e-mail is confidential. This e-mail is intended only for the stated addressee.  If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. if you have received this e-mail in error, please inform us immediately and delete it and all copies from your system.

EBS Dealing Resources International Limited. Registered address: 2 Broadgate, London EC2M 7UR, United Kingdom. Registered number 2669861.

EBS Dealing Resources, Inc, registered in Delaware. Address: Harborside Financial Center, 1100 Plaza Five, 12th Floor Jersey City, New Jersey 07311-4996 and One upper Pond road, Building F - Floor 3, Parsippany, NJ 07054, USA.

EBS Dealing Resources Japan Limited, a Japanese Corporation. Address: Asteer Kayabacho Bldg, 6th Floor, 1-6-1, Shinkawa, Chuo-Ku,  Tokyo 104-0033, Japan.