Perforce: Find source changelist for a branch

Short version:

After branching in P4, how can I find out the "source" changelist of the branch?

Long version:

Let's say I have a main branch of my project at

//project/main/...

The latest changelist submitted here is @123, when I decide to create a branch for release 1.0 in

//project/1.0/...

From P4V, a new changelist is created (say @130), resolved and submitted.

From the CLI, it would look something like this:

p4 integrate -c 123 -o //project/main/... //project/1.0/...p4 submit

Later, I look at the changelists under //project/1.0, and see the @130 changelist containing a lot of branched files. How can I find out the changelist no. that this was originally branched from (that is, @123) ?

View the original article here

Where does Hudson store its last synchronized Perforce changelist number?

One of our Hudson build systems is not automatically starting its jobs since we switched it over to a different Perforce server. The polling log reports:

Last sync'd change was nnnnnn

Where nnnnnn is a changelist number from the old server. The new server has lower CL numbers, which causes the problem.

How do I adjust the CL number that Hudson compares against?

View the original article here

Put P4 move operation in a non default changelist

You can use p4 opened to see the status of the opened files in your changelist. The following sequence of commands illustrates what happens during a p4 move.

$ p4 open icons.zip$ p4 opened //full/depot/path/to/icons.zip#1 - edit default change (ubinary)$ p4 move icons.zip foo.zip//full/depot/path/to/foo.zip#1 - moved from //full/depot/path/to/icons.zip#1$ p4 opened//full/depot/path/to/foo.zip#1 - move/add default change (ubinary)//full/depot/path/to/icons.zip#1 - move/delete default change (ubinary)$ p4 changelist Change 350425 created with 2 open file(s).$ p4 opened//full/depot/path/to/foo.zip#1 - move/add change 350425 (ubinary)//full/depot/path/to/icons.zip#1 - move/delete change 350425 (ubinary)

As you can see, the creation of a new pending changelist didn't change the status of the opened files at all, it pertains the move/add + move/delete action. If this is not what you were looking for, please edit your question.

Note: the above was tested with P4D/2009.2 (Server) and p4/2010.1 (Client).

View the original article here