[p4] Query on getting the required versions of the versioned files as required for the build

[Bhattacharya, Debapriya (Wipro)]

Hi,

Many thanks for the excellent solutions you have provided.
I will soon be in a position to find out what works good for this
project.

Regards,
Deb

-----Original Message-----
From: Weintraub, David [mailto:david.weintraub at bofasecurities.com] 
Sent: 13 September 2006 16:26
To: Bhattacharya, Debapriya (Wipro); perforce-user at perforce.com
Subject: RE: [p4] Query on getting the required versions of the
versioned files as required for the build

You can use a label to mark which files you want in a build, then do a
sync from the label. If you're using Ant, you can use a *.properties
file to set up your sync argument. Normally, this would be "#head", but
you'd be able to change it in times like this.

Another solution is to make a new branch with the code you want. Create
a label to mark the files you want, then do a "p4 integrate -b
<buildSpec> -s //...@<label>" to create the new branch. This way, you
can copy your ant build files on that branch, and since the relationship
between the files in that branch, and the build.xml file hasn't changed,
you'd be able to build without making any modifications to your
build.xml file.

Normally, your build branch should only contain the code you want to
build. Checkpoints, experiments, and not-ready-for-the-current-build
features should all be done on side branches. My philosophy is that each
and every version of every file on the build branch should be more
feature ladened, better coded, and more bug free than the previous
version. To me, every build is a potential release candidate.

Occasionally, bad code gets checked into the build branch. In those
cases, I demand that the developer fixes it immediately, and if they
can't, to copy the code to a side branch, and I'll obliterate those
revisions from the build branch. That way, I am always building from
#head.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Bhattacharya,
Debapriya (Wipro)
Sent: Monday, September 11, 2006 12:40 PM
To: perforce-user at perforce.com
Subject: [p4] Query on getting the required versions of the versioned
files as required for the build

Hi,

I need to perform a build such that among all the files in the directory
tree in my Perforce project, some files should be of the latest version
and some files should be of the chosen versions earlier than the latest
ones.

Following is an example:

Folder	File	Versions	 Version required for build	Comment	
Folder 1					
	File 10	1,2,3,4,5	5	Latest Version	
	File 11	1,2,3	3	Latest Version	
	File 12	1,2,3,4	3	Earlier Version	
Folder 2					
	File 20	1,2,3,4	4	Latest Version	
	File 21	1,2,3,4	3	Earlier Version	
	File 22	1,2,3,4,5	1	Earlier Version	

Can some one please let me know the correct way of getting the required
versions of the files so that my ANT script can perform the build
without any changes to the script?

Regards,
Deb
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user