[JIRA] [cvs] (JENKINS-17965) CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8
Sascha Vogt commented on JENKINS-17965 CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8 For us it seemed that using the forceCleanCopy flag resulted in sticky checkouts (have a look into the workspace, are there files with a # and version numbers in the name?) Wiping the workspace and disabling the flag helped... 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/groups/opt_out.
[JIRA] [cvs] (JENKINS-17965) CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8
K P commented on JENKINS-17965 CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8 So it looks like your files aren't updated when the "use update" (-C) flag is set, though the changelog sees the changes? Looks the same issue as the one we're having in JENKINS-17383 which essentially means that option -C doesn't work. 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/groups/opt_out.
[JIRA] [cvs] (JENKINS-17965) CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8
Joel Wheeler commented on JENKINS-17965 CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8 Yes, exactly- the files arent updated when "use updated" flag is set, tho the changelog sees the changes. I'm not sure where you determine that it uses the -C flag? It works in plugin version 1.6 but not in v2.8. Is there a different flag used in the different versions, or just a different implementation of how that flag works? I'm not sure if Jenkins uses it's own CVS implementation or the one installed on the system. 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/groups/opt_out.
[JIRA] [cvs] (JENKINS-17965) CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8
Joel Wheeler commented on JENKINS-17965 CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8 Just read thru your bug post. If I am remembering the situation correctly, I think one difference between our two issues are that my polling logs show "No changes detected" when it polls CVS- so mine never even attempts the update. Your logs show that the a change is detected but the update is not updating. 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/groups/opt_out.
[JIRA] [cvs] (JENKINS-17965) CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8
Joel Wheeler edited a comment on JENKINS-17965 CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8 Yes, exactly- the files arent updated when "use updated" flag is set, tho the changelog sees the changes. 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/groups/opt_out.
[JIRA] [cvs] (JENKINS-17965) CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8
Joel Wheeler created JENKINS-17965 CVS updates not working correctly after upgrading CVS plugin from v1.6 to 2.8 Issue Type: Bug Assignee: Unassigned Components: cvs Created: 15/May/13 3:11 PM Description: I upgraded to CVS plugin version 2.8 from 1.6, and also ran the 'Manage Old Data' process from the Manage Jenkins screen. After the update, some projects were not retrieving changes that were committed to CVS and putting them into the workspace. If I clicked on the 'Recent Changes' link in Jenkins for the job, the changes would appear there, but they were not being pulled into the workspace and CVS polling log showed 'no changes'. For some projects this was not an issue, but for other projects it was. I checked the config files, and some had been updated to the 2.8 format and some still had the 1.6 format. The jobs that had been updated to the 2.8 format were the ones that were not pulling newly committed files into the workspace. It looks like the bug occurs when the config files use the 2.8 plugin format and the 'Use Update' option is selected (canUseUpdatetrue/canUseUpdate). I deselected this option, and also selected 'Force clean copy for locally modified files' (cleanOnFailedUpdatetrue/cleanOnFailedUpdate). The files then began to be correctly updated in the workspace. Here is a config file example where the 1.6 plugin format is used (and continues working with the 2.8 plugin installed): scm class="hudson.scm.CVSSCM" plugin="cvs@1.6" cvsroot:pserver:u...@server.com:/cvsroot/stuff/cvsroot moduleExModule/module canUseUpdatetrue/canUseUpdate useHeadIfNotFoundfalse/useHeadIfNotFound flattenfalse/flatten isTagfalse/isTag excludedRegions/excludedRegions /scm And here is a config file example where the 2.8 plugin format is used and the files do not get updated when there is a commit to CVS: scm class="hudson.scm.CVSSCM" plugin="cvs@2.8" flattentrue/flatten repositories hudson.scm.CvsRepository cvsRoot:pserver:u...@server.com:/cvsroot/stuff/cvsRoot repositoryItems hudson.scm.CvsRepositoryItem modules hudson.scm.CvsModule localName/localName remoteNameExJob2/remoteName /hudson.scm.CvsModule /modules location class="hudson.scm.CvsRepositoryLocation$HeadRepositoryLocation" locationTypeHEAD/locationType useHeadIfNotFoundfalse/useHeadIfNotFound /location /hudson.scm.CvsRepositoryItem /repositoryItems compressionLevel-1/compressionLevel excludedRegions hudson.scm.ExcludedRegion pattern/pattern /hudson.scm.ExcludedRegion /excludedRegions passwordiLig231CAGwVtdt2/P6vseSiX+rCNjWwXG4/sAyjj1c=/password passwordRequiredtrue/passwordRequired /hudson.scm.CvsRepository /repositories canUseUpdatetrue/canUseUpdate skipChangeLogfalse/skipChangeLog pruneEmptyDirectoriestrue/pruneEmptyDirectories disableCvsQuiettrue/disableCvsQuiet cleanOnFailedUpdatefalse/cleanOnFailedUpdate forceCleanCopytrue/forceCleanCopy /scm after changing to these values in the 2.8 plugin format: canUseUpdatefalse/canUseUpdate cleanOnFailedUpdatetrue/cleanOnFailedUpdate it appeared to start working again. I think it was because of the canUseUpdate flag. Environment: Jenkins 1.510, CVS plugin 2.8, Linux RHEL 5 Project: Jenkins Labels: plugin cvs update jenkins Priority: Major Reporter: Joel Wheeler
