[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Title: Message Title Rob Dutton commented on JENKINS-26506 Re: Auto cleanup and sync as well as sync only are not reliable I've run into this too. I'm trying to use a single Perforce workspace over more than one Jenkins job using the Custom Workspace option, but I'm also seeing some files not sync correctly between the builds. Since the jobs always work on the same project data it seemed a no-brainer to do this - and I'm not sure I understand why there are multiple databases at play in this situation? Definitely sounds like a bug. To get around this I've had to create multiple workspaces, one for each job, but now none of the build steps can be shared with each other. Are there any further updates on fixing this issue? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable Has anyone tried the latest snapshot release (build 163)? https://jenkins.ci.cloudbees.com/job/plugins/job/p4-plugin/163/org.jenkins-ci.plugins$p4/ This has extra logging which might highlight the error/warning explaining why the file is not synced. The AutoCleanImpl process is quite complicated: ClientHelper.java 1. revert open files (typically a shelf) 2. delete any files that were open for added 3. reconcile -naedlf (to clean up Add/Edit/Deletes) 4. if needed force sync any missing files from step 3 If there are enough users on 14.1 I can simplify most of the steps with a 'p4 clean'. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Evan Benn commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable The method of sharing workspaces between jobs works fine with the other jenkins perforce plugin. It requires duplicating the custom workspace and perforce client name between the jobs. It is also essential to ensure only one job can be running at a time. I am using this method on multiple matrix jobs with many agents. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I understand your need to save space, but Perforce and the p4 plugin were not designed to share workspaces in quite this way. The server stores a have list (db.have) of the files that have been synced into the workspace. When you use the same workspace with two Jenkins jobs, the p4 plugin switched the workspace root to the Jenkins job build location, but uses the same have list server side. If you set the Workspace root to the same location, then you might have some success, but you must limit the jobs to single execution and use Auto clean/Sync. Another solution might be to use three Perforce workspaces (each with their own Jenkins jobs) one for the common art assets and the other two for the projects (lets call them A and B). Then use symlinks to bring the art assets into the projects for A and B (or instead of symlinks, update the build rules for the new location). For future solutions... I'm currently researching FlexClone with Perforce/Jenkins builds; it requires a NetApp storage, but there may be other similar solutions for other storage vendors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Matthew Smith commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I actually do have the workspace roots set to the same location, the problem is that the db have is being updated but not actually syncing files, this seems like a bug, since it definitely detects the changes in the depot, but doesn't actually update the files on disk. I've gotten around this issue by having one job that does the syncing that is called from the other jobs, and when that completes, the jobs run whatever steps the user originally requested. It's annoying, and a little obfuscated, but we can still limit executors meaningfully enough to let things happen in serial they way they currently need to on this box. We're doing some work internally to bring online a massive storage array, but that introduces other issues with having the files synced and replicated or referenced on the server. Thanks for the response! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Matthew Smith commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I am running into this problem as well. The reason I am trying to have one workspace shared across multiple jobs is due to the size of the particular depot. We can't get enough space on a slave machine to have multiple stored versions of the same code/content/art. P4 Streams would make our lives easier, but our release cadence prevents that work from getting done. What I will do in the meantime is set up a 'starter' project for the branch that updates the client workspace, then hand control off to the actual project the user meant to run. I would like to see a fix for this, we're limiting executor access to those directories by branch currently, so I am not worried about concurrent runs on the same slave node. He's a repro: in 1 job, in 1 workspace, sync a file Check in a change to that file in a separate job referencing the same workspace, trigger a build that syncs You will be able to observe the have entry for that file updates, but the file on disk will remain at rev 1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable Using the same workspace for different jobs is the problem. Perforce stores a 'have' list for each files synced into a workspace. The 'have' list is then used for subsequent syncs. If Perforce already thinks you have a file revision based on the 'have' list, it will not send you that file. Jenkins will use a different workspace root for each job e.g. c:\jenkins_home\job_1\ c:\jenkins_home\job_2\ If the same Perforce Workspace is used only one 'have' list is maintained, but the updates are now split across different paths. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Sebastiano Mandala edited a comment on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I am not sure if it's the real issue. When I use the same workspace on different jobs they all point to the same folder. I thought this was implicit, that's why I didn't specify it. I Use the Use custom workspace option to force using the same folder. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Sebastiano Mandala commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I am not sure if it's the real issue. When I use the same workspace on different jobs they all point to the same folder (I thought this was implicit, that's why I didn't specify it) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen edited a comment on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable Using the same workspace for different jobs is the problem. Perforce stores a 'have' list entry for each file synced into a workspace. The 'have' list is then used for subsequent syncs. If Perforce already thinks you have a file revision based on the 'have' list, it will not send you that file. Jenkins will use a different workspace root for each job e.g. c:\jenkins_home\job_1\ c:\jenkins_home\job_2\ If the same Perforce Workspace is used only one 'have' list is maintained, but the updates are now split across different paths. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I am not familiar with a custom workspace option to point Jenkins jobs to the same folder. Is this under the 'Advanced Project Options' - 'Use custom workspace' option? I'm not sure why you would need to do this and it seems dangerous to overlap directories. Could you provide some detail on your use-case, there may be a simpler alternative. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Sebastiano Mandala commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable My configuration is very simple. Just one jenkins installation without parallel jobs. I do use the same workspace for different jobs, but they never run together. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen
commented on JENKINS-26506
Auto cleanup and sync as well as sync only are not reliable
Are you using slave nodes or building on the jenkins master?
Do you have more than one executor or accidentally using the same workspace name for different jobs (I would suggest including ${JOB_NAME} as part of the workspace name).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Sebastiano Mandala created JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 20/Jan/15 10:54 AM Description: It's not easy to give details for this specific bug, but often, if I don't use force sync mode, after a few sync, the workspace is not actually synced with the files on the server. This means that one or more files fail to sync properly, without perforce communicating any specific error. It happens even if the clobber option is enabled. Not sure how to reproduce it, but it usually happens after few working sync. Project: Jenkins Priority: Major Reporter: Sebastiano Mandala This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Sebastiano Mandala updated JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable Change By: Sebastiano Mandala (20/Jan/15 10:56 AM) Environment: Windows7,java1.7,version1.1.2,p4serverversion:P4D/NTX86/2012.2/585708(2013/02/01),jenkins1.596 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
