-
Bug
-
Resolution: Unresolved
-
Major
-
p4-plugin 1.8.5
Jenkins 2.105
I have a Perforce stream called //UE4/main and in a subdirectory I have the SteamCMD utility.
To use the steamcmd utility I defined a job that maps that specific directory to the workspace only, like so:
Unfortunately, when this job was ran, the resulting workspace was like so:
Which resulted in an unnecessary download of about 13 80 Gb of content (when I only needed 2 Mb).
I don't think I specified the view incorrectly (essentially, it should have only synced Tools/BuildScripts/Uploaders/Steam/ to the workspace folder Steam).
[JENKINS-49483] When using Streams, custom view definition seems to be ignored
Description |
Original:
I have a Perforce stream called //UE4/main and in a subdirectory I have the SteamCMD utility. To use the steamcmd utility I defined a job that maps that specific directory to the workspace only, like so: !image-2018-02-09-15-50-47-532.png! Unfortunately, when this job was ran, the resulting workspace was like so: !image-2018-02-09-15-51-33-153.png! Which resulted in an unnecessary download of about 13 Gb of content (when I only needed 2 Mb). I don't think I specified the view incorrectly (essentially, it should have only synced Tools/BuildScripts/Uploaders/Steam/ to the workspace folder Steam). |
New:
I have a Perforce stream called //UE4/main and in a subdirectory I have the SteamCMD utility. To use the steamcmd utility I defined a job that maps that specific directory to the workspace only, like so: !image-2018-02-09-15-50-47-532.png! Unfortunately, when this job was ran, the resulting workspace was like so: !image-2018-02-09-15-51-33-153.png! Which resulted in an unnecessary download of about -13- 80 Gb of content (when I only needed 2 Mb). I don't think I specified the view incorrectly (essentially, it should have only synced Tools/BuildScripts/Uploaders/Steam/ to the workspace folder Steam). |
Labels | Original: plugin scm | New: P4_SUPPORT |
Comment |
[ I have this same issue. This seems pretty limiting. The problem here is that submit will fail if you don't define the stream due to this issue: [https://stackoverflow.com/questions/12731649/perforce-error-cannot-submit-from-non-stream-client] I'm doing this in a Jenkins pipeline ] |
Assignee | New: Paul Allen [ p4paul ] |