[JIRA] [subversion-plugin] (JENKINS-10222) Jenkins cleaning out workspace unnecessarily when polling SCM (SVN)
Alexandru Gheorghe edited a comment on JENKINS-10222 Jenkins cleaning out workspace unnecessarily when polling SCM (SVN) Same issue as Damien Finck described we're encoutering with latest Jenkins version to this date: v1.602: subversion plugin: 2.5 multiple repositories: some fetched to different folders the rest fetched to one folder each time there's a trigger (timed at 15 minutes) even if there are no changes polling takes place the checkout will delete files and add ones on the first poll of the first repository, then the second does the same; what is interesting is that in the end it will balance out and it'll work but each time the build is triggered it will fetch the files in the workspace at each 15 minutes a new build takes 11MB so that in a couple of days we got over 1GB of disk space occupied; not something wanted Tried to append @HEAD at the URL but no luck: https://url/svn/branch@HEAD , it will indeed go to HEAD and poll there (unlike before where the revision was the date at which it was started) but still with "No changes" in the subversion polling log it still gets the files and checks out as if it goes back 1 revision and sees new 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/d/optout.
[JIRA] [subversion-plugin] (JENKINS-10222) Jenkins cleaning out workspace unnecessarily when polling SCM (SVN)
Alexandru Gheorghe commented on JENKINS-10222 Jenkins cleaning out workspace unnecessarily when polling SCM (SVN) Same issue as Damien Finck described we're encoutering with latest Jenkins version to this date: v1.602: subversion plugin: 2.5 multiple repositories: some fetched to different folders the rest fetched to one folder each time there's a trigger (timed at 15 minutes) even if there are no changes polling takes place the checkout will delete files and add ones on the first poll of the first repository, then the second does the same; what is interesting is that in the end it will balance out and it'll work but each time the build is triggered it will fetch the files in the workspace at each 15 minutes a new build takes 11MB so that in a couple of days we got over 1GB of disk space occupied; not something wanted 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] [subversion-plugin] (JENKINS-10222) Jenkins cleaning out workspace unnecessarily when polling SCM (SVN)
Alan Birtles commented on JENKINS-10222 Jenkins cleaning out workspace unnecessarily when polling SCM (SVN) just had a similar issue, in our case we had the svn url defined as http://server:80/svn/repo, I think the svn checkout strips out the port number then the polling thinks that the workspace doesn't contain the same working copy. 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.
