[JIRA] (JENKINS-57870) populate: previewOnly(quiet: true) fail

[luckyhk.lee@samsung.com (JIRA)]

Hokwang Lee created an issue

Jenkins / JENKINS-57870 populate: previewOnly(quiet: true) fail Issue Type: Bug Assignee: Paul Allen Components: p4-plugin Created: 2019-06-06 00:52 Environment: Jenkins ver. 2.164.3 p4-plugin : 1.10.0 Priority: Blocker Reporter: Hokwang Lee Hi,   When I use jenkins with swarm automated test, I use the pipeline code like checkout perforce(    populate: previewOnly(quiet: true)    workspace: templateSpec( ... ) ) and template workspace have all depot like //depotA/... //$P4_CLIENT/depotA/... //depotB/... //$P4_CLIENT/depotB/... //depotC/... //$P4_CLIENT/depotC/... ... and I create new workspace and delete after finished job always.   as you know, because I want to do like unshelve files in the review item and run some test. I don't need sync, sync -n or sync -k and flush, delete, whatever..   here's error message. [Pipeline] container[Pipeline] {[Pipeline] checkout*02:02:57* (p4):cmd:... p4 client -o TEMPLATE_SE_SWARM_AT_SA*02:02:57* p4 client -o TEMPLATESE_SWARM_AT_SA*02:02:57* 02:02:57 (p4):stop:3*02:02:57* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:57* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:57* 02:02:58 (p4):stop:4*02:02:58* (p4):cmd:... p4 client -i*02:02:58* p4 client -i*02:02:58* 02:02:58 Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved.02:02:58 02:02:58 (p4):stop:5*02:02:58* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:58* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:58* 02:02:58 (p4):stop:6*02:02:58* (p4):cmd:... p4 client -i*02:02:58* p4 client -i*02:02:58* 02:02:58 Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved.02:02:58 02:02:58 (p4):stop:7*02:02:58* (p4):cmd:... p4 client -f -s -t TEMPLATESE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at-s_02:02:58 p4 client -f -s -t TEMPLATESE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:58* 02:02:58 Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z switched.02:02:58 02:02:58 (p4):stop:8*02:02:58* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:58* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:58* 02:02:59 (p4):stop:9*02:02:59* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:59* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:59* 02:02:59 (p4):stop:10*02:02:59* (p4):cmd:... p4 counter change*02:02:59* p4 counter change*02:02:59* 02:02:59 (p4):stop:11*02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/._02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...02:02:59 02:02:59 Change 2688516 on 2019/06/05 by sj828...@sj8282.park_NOVUS_TASK_SVR19A_mare03 'Add Test Case Template with reg'02:02:59 (p4):stop:12*02:02:59* (p4):cmd:... p4 counter change*02:02:59* p4 counter change*02:02:59* 02:02:59 (p4):stop:13*02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/.__02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516*02:02:59* 02:05:28 Operation 'user-changes' failed.02:05:28 Request too large for server memory (try later?).02:05:28 02:05:28 (p4):stop:14   I need the option that create workspace without any changes, counter, ... other commands. And by the way, this preview option is really needed? who want to use p4 sync -nq , it's useless. and p4 sync -n command also. I don't know when and why use this option. Add Comment

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

[kwirth@perforce.com (JIRA)]

Karl Wirth commented on JENKINS-57870

Re: populate: previewOnly(quiet: true) fail Hi Hokwang Lee - This looks like a server error: 02:02:59 p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516

02:05:28 Operation 'user-changes' failed.02:05:28 Request too large for server memory (try later?).

I will therefore contact you directly to get more confidential information about the system and setup.

Add Comment

[pallen@perforce.com (JIRA)]

Paul Allen commented on JENKINS-57870

Re: populate: previewOnly(quiet: true) fail

If you are using PreviewOnly with the quiet option set then the sync operation is skipped and you should see "P4 Task: skipping sync." in the log. (since version 1.9.5) // Skip `p4 sync -q -n` to save compute time. if (populate.isQuiet()) { log("P4 Task: skipping sync."); return; } Jenkins still needs to know what changes are associated with the build; this is for reporting, but also for polling calculations. p4 changes -m1 -ssubmitted //CLIENT_SPEC/...@nnnn Should not cause the server to report 'Request too large for server memory (try later?)'.  Please work with our support team to get a copy of the Server log.

Add Comment

[kwirth@perforce.com (JIRA)]

Karl Wirth assigned an issue to Karl Wirth

Jenkins / JENKINS-57870 populate: previewOnly(quiet: true) fail

Change By: Karl Wirth Assignee: Paul Allen Karl Wirth

Add Comment

[kwirth@perforce.com (JIRA)]

Karl Wirth updated an issue

Jenkins / JENKINS-57870 populate: previewOnly(quiet: true) fail

Change By: Karl Wirth Labels: P4_SUPPORT

Add Comment

[pallen@perforce.com (JIRA)]

Paul Allen commented on JENKINS-57870

Re: populate: previewOnly(quiet: true) fail

Please can you also include the client view mappings when reporting to support.  (Exclusionary mappings could be very expensive.)

Add Comment

[kwirth@perforce.com (JIRA)]

Karl Wirth updated an issue

Jenkins / JENKINS-57870 populate: previewOnly(quiet: true) fail Change By: Karl Wirth

Hi,   When I use jenkins with swarm automated test, I use the pipeline code like

{code:java}

checkout perforce(    populate: previewOnly(quiet: true)    workspace: templateSpec( ... ) )

{code}

and template workspace have all depot like

{code:java}

//depotA/... //$P4_CLIENT/depotA/... //depotB/... //$P4_CLIENT/depotB/... //depotC/... //$P4_CLIENT/depotC/... ...

{code}

and I create new workspace and delete after finished job always.   as you know, because I want to do like unshelve files in the review item and run some test. I don't need sync, sync -n or sync -k and flush, delete, whatever..   here's error message.

{code:java} [Pipeline] container[Pipeline] {[Pipeline] checkout* 02:02:57*  (p4):cmd:... p4 client -o TEMPLATE__SE_SWARM_AT_SA TEMPLATE_SE_SWARM_AT_SA * 02:02:57*  p4 client -o TEMPLATE__SE_SWARM_AT_SA TEMPLATESE_SWARM_AT_SA * 02:02:57* * 02:02:57 *   (p4):stop:3* 02:02:57*  (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:57*  p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:57* * 02:02:58 *   (p4):stop:4*

02:02:58*  (p4):cmd:... p4 client -i* 02:02:58*  p4 client -i*

02:02:58* * 02:02:58 *   Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved. * 02:02:58 * * 02:02:58 *   (p4):stop:5*

02:02:58*  (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:58*  p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*

02:02:58* * 02:02:58 *   (p4):stop:6*

02:02:58*  (p4):cmd:... p4 client -i* 02:02:58*  p4 client -i*

02:02:58* * 02:02:58 *   Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved. * 02:02:58 * * 02:02:58 *   (p4):stop:7* 02:02:58*  (p4):cmd:... p4 client -f -s -t TEMPLATE__SE_SWARM_AT_SA TEMPLATESE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at- s___* s_ 02:02:58 *   p4 client -f -s -t TEMPLATE__SE_SWARM_AT_SA TEMPLATESE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:58* * 02:02:58 *   Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z switched. * 02:02:58 * * 02:02:58 *   (p4):stop:8*

02:02:58*  (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:58*  p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*

02:02:58* * 02:02:59 *   (p4):stop:9*

02:02:59*  (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:59*  p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*

02:02:59* * 02:02:59 *   (p4):stop:10*

02:02:59*  (p4):cmd:... p4 counter change* 02:02:59*  p4 counter change*

02:02:59* * 02:02:59 *   (p4):stop:11* 02:02:59*  (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/. ___* _ 02:02:59 *   p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/... * 02:02:59 * * 02:02:59 *   Change 2688516 on 2019/06/05 by sj828...@sj8282.park_NOVUS_TASK_SVR19A_mare03 'Add Test Case Template with reg' * 02:02:59 *   (p4):stop:12*

02:02:59*  (p4):cmd:... p4 counter change* 02:02:59*  p4 counter change*

02:02:59* * 02:02:59 *   (p4):stop:13* 02:02:59*  (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/. ___* __ 02:02:59 *   p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/...@2688516* 02:02:59* * 02:05:28 *   Operation 'user-changes' failed. * 02:05:28 *   Request too large for server memory (try later?). * 02:05:28 * * 02:05:28 *   (p4):stop:14 {code}

I need the option that create workspace without any changes, counter, ... other commands. And by the way, this preview option is really needed? who want to use p4 sync -nq , it's useless. and p4 sync -n command also. I don't know when and why use this option.

Add Comment