When running "p4 reconcile" command.
It returns following error:
Client doesn't have necessary support for reconcile.
What it means? p4v can do reconcile on the same PC.
P4 reconcile requires at least version 2012.1.
Taken from the Perforce Blog:
The 2012.1 release of Perforce is just about to be released for beta. It's loaded with great new features. One is the p4 reconcile command, with its fraternal twin, p4 status.
Related
When issuing a p4 command e.g. p4 client no matter current working directory is inside or outside the perforce workspace, the command output is
Error: p4 client root is not '/workspace_dir'.
Please make sure that your Perforce workspace has the 'Alt roots' set to '/workspace_dir'.
P4V client works ok.
How can change 'Alt roots' setting?
Run the p4 client command to edit your AltRoots.
If you do not have multiple client roots (which is a pretty rare situation), you do not need to set the AltRoots field. The error you quote is not a Perforce error that I'm familiar with and may be some sort of wrapper script or trigger that is configured to expect an AltRoot for reasons that may not be sound. I'd check with your Perforce admin for clarification.
I just did a
p4 integrate -r -b Feature-to-Main
followed by
p4 resolve -as
to bring a feature branch up to date. However, I had forgot to commit my changes to the feature branch, so I was asked to resolve conflicts between changes done to Main and my uncommitted changes. Luckily, the changes were not on the default changelist, so I was able to undo all this by reverting the default changelist and choosing "select target" for all conflicts in the remaining changelists.
I do not like this behavior, and I wish that Perforce had not allowed me to execute the first command. Is it possible to configure Perforce to only perform integrations into workspaces with empty changelists?
Scenario:
I have a folder of files that are generated by an external tool that we check into Perforce for revision control, however we don't have knowledge ahead of time about when it's going to add/remove files from that structure.
So today our workflow is to checkout the entire directory, and then allow the tool to regenerate all of the files/hierarchy. When I run the reconcile command it successfully finds new files, but it fails to find files that were deleted.
Is there a better way to handle this?
Upgrade your Perforce server to 2014.2:
http://www.perforce.com/perforce/doc.current/user/relnotes.txt
Minor new functionality in 2014.2
#841159 **
'p4 reconcile' will now detect files that are open for edit but
missing from the client, and reopen them for delete.
A workaround is to do "p4 revert -k" prior to "p4 reconcile" so that it'll start over from scratch. The "-k" option tells revert to forget the files are open but NOT to actually undo the local changes.
A modified workflow that might make more sense if you're already using "p4 reconcile" religiously is to skip the "p4 edit" and use either the "allwrite" client spec option or the "+w" filetype modifier to make the files writable.
how to check if any changelist of project A is integrated in project B? and also to get corresponding submitted Cl in project B. Please share any perforce command
It's worth pointing out the unit of integration in P4 is files, not changelists, so the p4 commands are mostly focused around telling you which files are integrated or not. You can, however, find out which changelists still have some files that need to be integrated - use the p4 interchanges command. The Perforce docs explain the syntax.
Assuming that you have a branch spec that describes the relationship of project A and project B called projAprojB, then you can get the outstanding changelists with:
p4 interchanges -b projAprojB
You can also get a similar view of outstanding changes in the P4V Merge/Integrate dialog box.
Alternatively, you can use the 'revision graph' in P4V to see the integrations performed on a given file; doing this on a file from the changelist you want to know about will give you the information to work out if it has been integrated into the other project and the changelist for that was.
If this doesn't suit your needs then your only option is to write a script, either with shell scripting using p4 or one of the APIs provided by Perforce
Our user performed an integration between branches.
Integrated files were placed in a pending changelist but they are invisible when I look
at this changelist in p4v.
I can see them when I look on this changelist when I connected to another workspace, I can also see then in Eclipse.
When I choose to Resolve conflicts on this changelist it works too, but
when I try to submit the changes, there is nothing there.
After I installed a new version of p4v, the problematic pending
changelist appeared with a question mark (red triangle with a question
mark).
Any Ideas?
Thanks.
Answer from Perforce support:
This may be a working and locks out of sync
issue. Can you run the following server command:
p4d -r $P4ROOT -xf 925
Where "$P4ROOT" is the location of the db.* files.
P4V.exe allows the user to specify a filter on his workspace. Perhaps the workspace had a filter applied, such that the GUI did not show the files, where the command line client and others (ie Eclipse) would not be privy to this filter and would show the files.
Another possibility is that the user was logged in under a workspace other than his default, and the files were checked out in his default workspace. It would be easy to then find these files in his default by looking at pending changelists for all users.