[JIRA] (JENKINS-49483) When using Streams, custom view definition seems to be ignored

[htwiz2002@gmail.com (JIRA)]

Harry Takata created an issue

Jenkins / JENKINS-49483 When using Streams, custom view definition seems to be ignored Issue Type: Bug Assignee: Unassigned Attachments: image-2018-02-09-15-50-47-532.png, image-2018-02-09-15-51-33-153.png Components: p4-plugin Created: 2018-02-09 22:54 Environment: p4-plugin 1.8.5 Jenkins 2.105 Labels: plugin scm Priority: Major Reporter: Harry Takata 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 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). Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[htwiz2002@gmail.com (JIRA)]

Harry Takata updated an issue

Jenkins / JENKINS-49483 When using Streams, custom view definition seems to be ignored

Change By: Harry Takata

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).

Add Comment

[pallen@perforce.com (JIRA)]

Paul Allen updated an issue

Jenkins / JENKINS-49483 When using Streams, custom view definition seems to be ignored

Change By: Paul Allen Labels: plugin scm P4_SUPPORT

Add Comment

[ben@2nproductions.com (JIRA)]

Ben L commented on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored 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

Add Comment

[ben@2nproductions.com (JIRA)]

Ben L edited a comment on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored

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

Add Comment

[ben@2nproductions.com (JIRA)]

Ben L updated an issue

Jenkins / JENKINS-49483

When using Streams, custom view definition seems to be ignored

Change By: Ben L 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

Add Comment

[delikat.mateusz@gmail.com (JIRA)]

Mateusz Delikat commented on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored We have this issue here too. It seems as if view mappings are being forced onto workspace view, but since it's specified as a stream workspace those can't be applied onto workspace specification. In old perforce plugin there were two "view maps" - one of those (when checked) could work as an overlay for jenkins to know what to sync and how to populate changeLogSet without interfering with workspace stream specification. This was ideal for situations like the one mentioned in this report.

Add Comment

[delikat.mateusz@gmail.com (JIRA)]

Mateusz Delikat edited a comment on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored

We have this issue here too.

It seems as if view mappings are being forced onto workspace view, but since it's specified as a stream workspace those can't be applied onto workspace its specification.

In old perforce plugin there were two "view maps" - one of those (when checked) could work as an overlay for jenkins to know what to sync and how to populate changeLogSet without interfering with workspace stream specification. This was ideal for situations like the one mentioned in this report.

Add Comment

[delikat.mateusz@gmail.com (JIRA)]

Mateusz Delikat edited a comment on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored

We have this issue here too.

It seems as if view mappings are being forced onto workspace view, but since it's specified as a stream workspace those can't be applied onto its specification.

In old perforce plugin there were two "view maps" - one of those (when checked) could work as an overlay for jenkins to know what to sync and how to populate changeLogSet without interfering with workspace stream specification. This was ideal for situations like the one mentioned in this report.

Add Comment

[delikat.mateusz@gmail.com (JIRA)]

Mateusz Delikat assigned an issue to Paul Allen

Jenkins / JENKINS-49483

When using Streams, custom view definition seems to be ignored

Change By: Mateusz Delikat Assignee: Paul Allen

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[pallen@perforce.com (JIRA)]

Paul Allen commented on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored I have a possible workaround using the 'Preview Check Only' option (sync -n ...), but for the moment it will require a 'Pipeline' build. You would need to create a Jenkinsfile and checkout the code using a Streams workspace with the 'Preview Check Only' option; then use a P4 Groovy step to sync just the files you need from the same workspace definition. If you think this will work, but you would prefer to use the older FreeStyle Jenkins job, I would need to add a sync step or you would have to call out to a script.

Add Comment

[delikat.mateusz@gmail.com (JIRA)]

Mateusz Delikat commented on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored

Is P4Groovy step going to update changeset for the build when used that way?

Add Comment

[pallen@perforce.com (JIRA)]

Paul Allen commented on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored

Unfortunately no; P4Groovy runs outside of Jenkins and will not update the built changes list. However the Preview Check Only option should record the changes and set the sync ID; this is used to report the changes in the build summary and record the SyncID used by polling to figure out if a build is required.

Add Comment

[delikat.mateusz@gmail.com (JIRA)]

Mateusz Delikat edited a comment on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored

[~p4paul]: Would it work, if I'd create a label my_label with revision field set as @X, where X is a changelist number submitted to stream {my_stream} with a view: * //{my_stream}/... * -//{my_stream}/{some_path}/... And then setting pin in p4sync to "@my_label,@my_label"? With "p4 sync //{my_stream}/...@{my_label}" it all files excluded from label are deleted, but with "p4 sync //{my_stream}/...@{my_label},@{my_label}" it looks like those excluded are left behind and not sync'ed, which basically is ideal. Does this construct work with p4sync pin feature?

Add Comment

[delikat.mateusz@gmail.com (JIRA)]

Mateusz Delikat commented on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored

Paul Allen: Would it work, if I'd create a label my_label with revision field set as @X, where X is a changelist number submitted to stream {my_stream} with a view: //{my_stream} /... -//

{my_stream}/{some_path}/... And then setting pin in p4sync to "@my_label,@my_label"? With "p4 sync //{my_stream} /...@ {my_label}" it all files excluded from label are deleted, but with "p4 sync //{my_stream}/...@{my_label} ,@ {my_label} " it looks like those excluded are left behind and not sync'ed, which basically is ideal. Does this construct work with p4sync pin feature?

Add Comment

[delikat.mateusz@gmail.com (JIRA)]

Mateusz Delikat edited a comment on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored

[~p4paul]: Would it work, if I'd create a label my_label with revision field set as @X, where X is a changelist number submitted to stream {my_stream} with a view: * // \ {my_stream}/... * -// \ {my_stream}/ \ {some_path}/...

And then setting pin in p4sync to "@my_label,@my_label"? With "p4 sync // \ {my_stream}/...@ \ {my_label}" it all files excluded from label are deleted, but with "p4 sync // \ {my_stream}/...@ \ {my_label},@ \ {my_label}" it looks like those excluded are left behind and not sync'ed, which basically is ideal. Does this construct work with p4sync pin feature?

Add Comment

[delikat.mateusz@gmail.com (JIRA)]

Mateusz Delikat edited a comment on JENKINS-49483

Re: When using Streams, custom view definition seems to be ignored

[~p4paul]: Would it work, if I'd create a label my_label with revision field set as @X, where X is a changelist number submitted to stream \{my_stream}

with a view: //\{my_stream}/...

-//\{my_stream}/\{some_path}/... And then setting pin in p4sync to "@my_label,@my_label"? With "p4 sync //\{my_stream}/...@\{my_label}" it all files excluded from label are deleted, but with "p4 sync //\{my_stream}/...@\{my_label},@\{my_label}" it looks like those excluded are left behind and not sync'ed, which basically is ideal. Does this construct work with p4sync pin feature?

Add Comment

[delikat.mateusz@gmail.com (JIRA)]