[ https://issues.jenkins-ci.org/browse/JENKINS-13027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160146#comment-160146 ]
Richard Taylor commented on JENKINS-13027: ------------------------------------------ Hi Rob, Thanks for getting back to me. It's actually failed again over the weekend. The issue appears to be orrucing every 1 to 2 days. I think a debug build is probably the best option as it looks like a strange problem. There is some info about the recient builds. We have a pool of 2 machines gbwwsrunbld08 and gbwwsrunbld09 for building packages. I got everything working on Friday and both machines build successful packages. The recient run of build is as follows. Failed #56 19 sec gbwwsrunbld08 Failed #55 32 sec gbwwsrunbld08 Failed #54 1 min 45 sec gbwwsrunbld08 Success #53 13 min gbwwsrunbld09 Success #52 9 min 35 sec gbwwsrunbld08 Success #51 6 min 3 sec gbwwsrunbld09 Success #50 6 min 11 sec gbwwsrunbld08 Success #49 7 min 52 sec gbwwsrunbld09 The parameters as recorded on the build summary page are the same for all builds. CHANGELIST = now BRANCH = branches/evo11dx11 SLAVE_LABEL = evo11release I've verified these against the build logs for the above builds and all params are present and correct as environment variables. >From the build log of #54 we see this 21:01:35 Using remote perforce client: jenkins_gbwwsrunbld08_evo11main 21:01:35 [evo11main] $ "c:\\program files\\perforce\\p4.exe" workspace -o jenkins_gbwwsrunbld08_evo11main 21:01:35 [evo11main] $ "c:\\program files\\perforce\\p4.exe" login -p 21:01:35 [evo11main] $ "c:\\program files\\perforce\\p4.exe" -P 831EC39454600F1AF16985DE3AD2AFCD workspace -o jenkins_gbwwsrunbld08_evo11main 21:01:35 Changing P4 Client View from: 21:01:35 //depot/evolution/evo11/branches/evo11dx11/... //jenkins_gbwwsrunbld08_evo11main/... 21:01:35 -//depot/evolution/evo11/branches/evo11dx11/MS3/....mb //jenkins_gbwwsrunbld08_evo11main/MS3/....mb 21:01:35 -//depot/evolution/evo11/branches/evo11dx11/MS3/....pds //jenkins_gbwwsrunbld08_evo11main/MS3/....pds 21:01:35 -//depot/evolution/evo11/branches/evo11dx11/MS3/....ma //jenkins_gbwwsrunbld08_evo11main/MS3/....ma 21:01:35 -//depot/evolution/evo11/branches/evo11dx11/MS3/....ZTL //jenkins_gbwwsrunbld08_evo11main/MS3/....ZTL 21:01:35 //depot/evolution/evo11/external/3rdParty/... //jenkins_gbwwsrunbld08_evo11main/3rdParty/... 21:01:35 //depot/evolution/evo11/external/Platform/... //jenkins_gbwwsrunbld08_evo11main/Platform/... 21:01:35 //depot/evolution/evo11/external/WWS/... //jenkins_gbwwsrunbld08_evo11main/WWS/... 21:01:35 -//depot/evolution/evo11/external/WWS/ATG/1.33.0/ATGTools/UnitTests/... //jenkins_gbwwsrunbld08_evo11main/WWS/ATG/1.33.0/ATGTools/UnitTests/... 21:01:35 21:01:35 Changing P4 Client View to: 21:01:35 //depot/evolution/evo11/external/3rdParty/... //jenkins_gbwwsrunbld08_evo11main/3rdParty/... 21:01:35 //depot/evolution/evo11/external/Platform/... //jenkins_gbwwsrunbld08_evo11main/Platform/... 21:01:35 //depot/evolution/evo11/external/WWS/... //jenkins_gbwwsrunbld08_evo11main/WWS/... 21:01:35 -//depot/evolution/evo11/external/WWS/ATG/1.33.0/ATGTools/UnitTests/... //jenkins_gbwwsrunbld08_evo11main/WWS/ATG/1.33.0/ATGTools/UnitTests/... 21:01:35 Saving modified client jenkins_gbwwsrunbld08_evo11main 21:01:35 [evo11main] $ "c:\\program files\\perforce\\p4.exe" -P 831EC39454600F1AF16985DE3AD2AFCD -s client -i 21:01:48 Last build changeset: 9913 21:01:48 [evo11main] $ "c:\\program files\\perforce\\p4.exe" -P 831EC39454600F1AF16985DE3AD2AFCD -s changes -s submitted -m 1 //jenkins_gbwwsrunbld08_evo11main/...@now 21:01:49 [evo11main] $ "c:\\program files\\perforce\\p4.exe" -P 831EC39454600F1AF16985DE3AD2AFCD -s changes -s submitted //jenkins_gbwwsrunbld08_evo11main/...@9914,@9930 21:01:49 [evo11main] $ "c:\\program files\\perforce\\p4.exe" -P 831EC39454600F1AF16985DE3AD2AFCD describe -s 9930 21:01:49 [evo11main] $ "c:\\program files\\perforce\\p4.exe" -P 831EC39454600F1AF16985DE3AD2AFCD -G where //... 21:01:50 Sync'ing workspace to label now. 21:01:50 [evo11main] $ "c:\\program files\\perforce\\p4.exe" -P 831EC39454600F1AF16985DE3AD2AFCD -s sync //jenkins_gbwwsrunbld08_evo11main/...@now 21:03:19 Sync complete, took 89265 ms The failed builds after this then continue to update the workspace and the client view is left in the broken state. 21:01:35 Using remote perforce client: jenkins_gbwwsrunbld08_evo11main 21:01:35 [evo11main] $ "c:\\program files\\perforce\\p4.exe" workspace -o jenkins_gbwwsrunbld08_evo11main 21:01:35 [evo11main] $ "c:\\program files\\perforce\\p4.exe" login -p 21:01:35 [evo11main] $ "c:\\program files\\perforce\\p4.exe" -P 831EC39454600F1AF16985DE3AD2AFCD workspace -o jenkins_gbwwsrunbld08_evo11main 21:01:35 Last build changeset: 9930 21:01:35 [evo11main] $ "c:\\program files\\perforce\\p4.exe" -P 831EC39454600F1AF16985DE3AD2AFCD -s changes -s submitted -m 1 //jenkins_gbwwsrunbld08_evo11main/...@now 21:01:37 Sync'ing workspace to label now. 21:01:37 [evo11main] $ "c:\\program files\\perforce\\p4.exe" -P 831EC39454600F1AF16985DE3AD2AFCD -s sync //jenkins_gbwwsrunbld08_evo11main/...@now 21:02:06 Sync complete, took 29370 ms Unfortunately the client view is not fixed by the next build. I'm going to switch back to using a slave name and not a label to see if the issue is related to hopping between 2 machines. Thanks > Perforce plugin will sometimes set an incorrect workspace view > -------------------------------------------------------------- > > Key: JENKINS-13027 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13027 > Project: Jenkins > Issue Type: Bug > Components: perforce > Affects Versions: current > Environment: Jenkins Master 1.454 OS Windows Server 2008 SP2 > Jenkins Slave 2.12 OS Windows Server 2008 R2 > Reporter: Richard Taylor > Assignee: Rob Petti > Fix For: current > > > Perforce plugin will sometimes set an incorrect workspace view. > The job has perforce Client View Type set to View Map with the following > details > //depot/evolution/evo11/${BRANCH}/... //workspace-name/... > -//depot/evolution/evo11/${BRANCH}/MS3/....mb //workspace-name/MS3/....mb > -//depot/evolution/evo11/${BRANCH}/MS3/....pds //workspace-name/MS3/....pds > -//depot/evolution/evo11/${BRANCH}/MS3/....ma //workspace-name/MS3/....ma > -//depot/evolution/evo11/${BRANCH}/MS3/....ZTL //workspace-name/MS3/....ZTL > //depot/evolution/evo11/external/3rdParty/... //workspace-name/3rdParty/... > //depot/evolution/evo11/external/Platform/... //workspace-name/Platform/... > //depot/evolution/evo11/external/WWS/... //workspace-name/WWS/... > -//depot/evolution/evo11/external/WWS/ATG/1.33.0/ATGTools/UnitTests/... > //workspace-name/WWS/ATG/1.33.0/ATGTools/UnitTests/... > The ${BRANCH} is set as a job parameter but the purposes of our current use > case it is always the same default value. > The job is set to run on a small pool of slaves with label. This pool of > slaved is used for building packages from diferent branches. > We get occasional build failures due to perforce incorrectly setting the > workspace view. These errors can only be fixed by a clean and sync. As a full > clean and sync takes 2 hours this is a significant issue. > ----- Jenkins build log ------ > 21:02:27 Started by timer > 21:02:27 Building remotely on gbwwsrunbld08 in workspace > c:\jenkins\workspace\evo11main > 21:02:27 Using remote perforce client: jenkins_gbwwsrunbld08_evo11main > 21:02:27 [evo11main] $ "c:\\program files\\perforce\\p4.exe" workspace -o > jenkins_gbwwsrunbld08_evo11main > 21:02:27 [evo11main] $ "c:\\program files\\perforce\\p4.exe" login -p > 21:02:27 [evo11main] $ "c:\\program files\\perforce\\p4.exe" -P > 831EC39454600F1AF16985DE3AD2AFCD workspace -o jenkins_gbwwsrunbld08_evo11main > 21:02:27 Changing P4 Client View from: > 21:02:27 //depot/evolution/evo11/branches/evo11dx11/... > //jenkins_gbwwsrunbld08_evo11main/... > 21:02:27 -//depot/evolution/evo11/branches/evo11dx11/MS3/....mb > //jenkins_gbwwsrunbld08_evo11main/MS3/....mb > 21:02:27 -//depot/evolution/evo11/branches/evo11dx11/MS3/....pds > //jenkins_gbwwsrunbld08_evo11main/MS3/....pds > 21:02:27 -//depot/evolution/evo11/branches/evo11dx11/MS3/....ma > //jenkins_gbwwsrunbld08_evo11main/MS3/....ma > 21:02:27 -//depot/evolution/evo11/branches/evo11dx11/MS3/....ZTL > //jenkins_gbwwsrunbld08_evo11main/MS3/....ZTL > 21:02:27 //depot/evolution/evo11/external/3rdParty/... > //jenkins_gbwwsrunbld08_evo11main/3rdParty/... > 21:02:27 //depot/evolution/evo11/external/Platform/... > //jenkins_gbwwsrunbld08_evo11main/Platform/... > 21:02:27 //depot/evolution/evo11/external/WWS/... > //jenkins_gbwwsrunbld08_evo11main/WWS/... > 21:02:27 > -//depot/evolution/evo11/external/WWS/ATG/1.33.0/ATGTools/UnitTests/... > //jenkins_gbwwsrunbld08_evo11main/WWS/ATG/1.33.0/ATGTools/UnitTests/... > 21:02:27 > 21:02:27 Changing P4 Client View to: > 21:02:27 //depot/evolution/evo11/external/3rdParty/... > //jenkins_gbwwsrunbld08_evo11main/3rdParty/... > 21:02:27 //depot/evolution/evo11/external/Platform/... > //jenkins_gbwwsrunbld08_evo11main/Platform/... > 21:02:27 //depot/evolution/evo11/external/WWS/... > //jenkins_gbwwsrunbld08_evo11main/WWS/... > 21:02:27 Saving modified client jenkins_gbwwsrunbld08_evo11main > As you can see perforce has removed the part view which was using the > ${BRANCH} parameter and has also remove the final -// line which was not > parameterised. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira