P4v integration error

Question

I created a new branch (N) from one of my code lines (A). Now I'm trying to integrate some files from another code line (B) that have the same tree structure in my new branch.

I use the Integrate parameter from the P4v GUI.Source - branch B and destination branch N, and use the branch specification to accomplish this.

During the integration, I am in the workspace with the N branch in my view, but the B branch is not displayed because it is on a different server.

I constantly get the following error Integration error - there is no target file (s) in the viewport

I searched on the net and many people are faced with this problem but have not found any solutions. Please, help.

Answer 1

The problem was that B was on a different server, and I did not have a remote depot mapping on the server containing A and N. Adding this mapping resolved the problem.

Answer 2

If you use P4V, you can easily make a mistake in the GUI. In particular, if you right-click somewhere to select "Merge / Integration ...", then what you clicked will be used as a target, EVEN IF YOU USE A BRANCH SPECIFICATION.

I was puzzled by something very similar to centuries, until I realized that I was pushing on branch B to start the merge, instead of clicking on branch N.

An incorrect GUI reference is what you clicked on, initially shown as a target, but when you decide to use the branch specification, this part of the dialog disappears. It is still present on the Filter tab, but you already forgot about it because the GUI took it ...

Answer 3

I assume these are not remote issues, as it gets the source branch using p4v and can choose the source and target for integration. I would rather check out your client view of the workspace.

the following error may also occur when your source and target representation of your integration should not be displayed in your workspace, which may not be available at present.

Answer 4

I had the same problem as a merge, like

p4 merge filename 

It so happened that the file was not in a branch created as a stream. Thus, he has no trace of the parent.

To fix this, I used the following command. Here I pointed out the devel_branch_name branch.

 p4 merge -b devel_branch_name filename 

I sat in the development branch.

Here is additional information .