Jump to content


danielku15

Member Since 04 Dec 2018
Offline Last Active Feb 04 2019 05:06 PM
-----

Posts I've Made

In Topic: Directory exclusion not working

04 February 2019 - 05:09 PM

Could be an idea. Thanks for the tip. I just hope I can really restrict the access to Git Fusion. In general it requires full admin privileges for the accounts being used. Not sure if I can revoke the access for admins. But its worth a shot.

In Topic: Exclude tree for p4 fetch

06 December 2018 - 10:10 AM

It seems that really only this one particular file was causing issues. The fact that we obliterated something in the past was leaving us in an inconsistent state regarding this Changelist. I decided to completely exclude the file from the migration and add it later again manually to the repository.

Thanks a lot for your assistance and from my side this topic is closed.

In Topic: Exclude tree for p4 fetch

06 December 2018 - 07:37 AM

Quote

Another possibility is that the admin obliterated the path that this file moved to
This sounds familiar. I think we asked the admin to obliterate some paths in the past because some things totally got messed up. An online research at that time mentioned to obliterate certain paths/files.

Maybe I really try to exclude this particular file and hope that nothing else pops up. The file only contains some unit tests where history might not be that important. I will update on this post once I have some new info.

Thanks so far.

In Topic: Exclude tree for p4 fetch

05 December 2018 - 10:05 AM

Thanks for the quick response. Maybe I was not precise enough in my explanation but yes, I understand that if you want to fetch some files, you need to ensure that you do not fetch half of the atomic operations. But still I have the feeling there are some prerequisites as I described them. Maybe it helps to solve my issue if I provide the actual error I am currently facing. I hope just posting all this details is fine here. In some forums people are not happy with that kind of "posting all details and screaming for help"-kind of posts :unsure:

I cleaned up again all my earlier tests and started from scratch to start with the initial error I get. I have the following remote spec for fetching:

//stream/OurProduct/Trunk/... //depot/OurSuite/OurSuite/OurProduct/...

//stream/OurProduct/SomeBranch/... //depot/OurSuite/OurSuite_SomeBranch/OurProduct/...

//stream/OurProduct/Release7.2/... //depot/OurSuite/OurSuite7.2/OurProduct/...

//stream/OurProduct/Release7.1/... //depot/OurSuite/OurSuite7.1/OurProduct/...

//stream/OurProduct/Release7.0/... //depot/OurSuite/OurSuite7.0/OurProduct/...

[Some more here...]


And I get this error when executing the fetch:

Change 750162 performs a move/delete on //depot/OurSuite/OurSuite_SomeBranch/OurProduct/src/SomeFile.cs#2, but the parameters of this fetch, push, or zip command include only part of the full action. Specify a wider view to include both the source and target of the change, or specify a narrower view to exclude both the source and target of the change.


When I look at the history of this file I see this:


D:\Dev>p4 filelog -i //depot/OurSuite/OurSuite_SomeBranch/OurProduct/src/Testing/SomeFile.cs#2

//depot/OurSuite/OurSuite_SomeBranch/OurProduct/src/Testing/SomeFile.cs

... #2 change 750162 move/delete on 2017/10/04 by user1@user1_OurSuiteTmp (utf8) 'Merging using OurSuite_SomeBranch '

... #1 change 744444 branch on 2017/09/12 by user2@user2_OurSuiteTmp (utf8) 'Merging OurSuite Trunk (All rest)'

... ... branch from //depot/OurSuite/OurSuite/OurProduct/src/Testing/SomeFile.cs#1,#3

//depot/OurSuite/OurSuite/OurProduct/src/Testing/SomeFile.cs

... #3 change 741082 edit on 2017/08/29 by user3@user3_OurProduct (utf8) 'Some other change'

... ... branch into //depot/OurSuite/OurSuite_SomeBranch/OurProduct/src/Testing/SomeFile.cs#1

... #2 change 738357 edit on 2017/08/17 by user3@user3_OurProduct (utf8) 'Some change'

... ... branch into //depot/OurSuite/OurSuite7.1/OurProduct/src/Testing/SomeFile.cs#1

... #1 change 738094 add on 2017/08/16 by user4@user4_OurProduct (utf8) 'Some initial change'


From what I see is that all trees are included in my spec. It is unfortunate that perforce detects that the fetch only includes partly the action, but then does not tell me which path is exactly missing so I could add it or dig further.


Regarding the reducing of the depth I already tried to cover that point in my initial post: As I plan to push to a server with Git Fusion enabled, I would like to have the full history available on this server as it helps the devs to understand why changes might were made in the past.

Edit 1:

When I look at the changes of 750162 I see on one site that there are integrations across many trees. For the SomeFile.cs where it complains the entries look like this:

File Name   | Revision | Action      | FileType | In Folder

SomeFile.cs | 3        | Integrate   | utf8     | //depot/OurSuite/OurSuite_SomeBranch/OurProduct/src/Infrastructure

SomeFile.cs | 2        | Move/Delete | utf8     | //depot/OurSuite/OurSuite_SomeBranch/OurProduct/src/Testing



After some further tests and additional filters, I also found the same error and a similar change that was happening on the trunk.


Change 748318 performs a move/delete on //depot/OurSuite/OurSuite/OurProduct/src/Testing/SomeFile.cs#6, but the parameters of this fetch, push, or zip command include only part of the full action. Specify a wider view to include both the source and target of the change, or specify a narrower view to exclude both the source and target of the change.File Name   | Revision | Action      | FileType | In Folder

SomeFile.cs | 10       | Integrate   | utf8     | //depot/OurSuite/OurSuite/OurProduct/src/Infrastructure

SomeFile.cs | 6        | Move/Delete | utf8     | //depot/OurSuite/OurSuite/OurProduct/src/Testing



There are 2 files with the same name in different folders, and they are unrelated. But maybe it has an impact.

There was a deletion of SomeFile.cs that cannot be fetched.