Sorry, if you don't have "execute concurrent builds" enabled, then I don't have any good suggestions to offer on the specific problem.
It sounds like your organization may prefer stability over frequent updates. If so, then you might consider using the long term support release, instead of using the most recent build. The long term support release only changes about 4 times a year, and it generally receives more attention to assure it is in very good condition before it is released. Mark Waite On Thu, Nov 21, 2013 at 4:17 PM, Erik Cokeley <ecoke...@zonoff.com> wrote: > I don't have the JGit plugin installed. None of my jobs have "Execute > concurrent builds if necessary" selected. > > On Thursday, November 21, 2013 6:09:07 PM UTC-5, Mark Waite wrote: >> >> If your Jenkins job is using the JGit implementation (rather than the Git >> command line implementation), then you may be seeing >> >> https://issues.jenkins-ci.org/browse/JENKINS-20286<https://www.google.com/url?q=https%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-20286&sa=D&sntz=1&usg=AFQjCNEOuM5wzbHOgDGYnWscMcIr8LueeQ> >> - >> polling reports changes when there are none >> >> I would expect that if a job is allowed to run multiple concurrent >> builds, and polls frequently, and mistakenly detects changes (when there >> are none), then the behavior you're seeing is what I would expect. >> >> If you're using the Git command line implementation, then I would not >> expect that bug to be the problem (since it is specific to the JGit >> implementation). >> >> In general, if you want to reduce disc space use and you have large git >> repositories, then you can consider using the "Advanced Clone Behaviours" >> setting to allow you to use a "reference" bare repository. That causes the >> workspace git repository to use pointers to most of the large files in the >> ".git" directory, instead of actually copying the files. That won't solve >> the root of your problem, but it may reduce your disc space used. >> >> Mark Waite >> >> >> >> On Thu, Nov 21, 2013 at 3:51 PM, Erik Cokeley <ecok...@zonoff.com> wrote: >> >>> I just updated Jenkins after a long time. Our company was always to >>> busy and worried about updated, we got devil jenkins a while back. After >>> updating all my ivy jobs started creating new workspaces (for example >>> workspace@2...) >>> >>> I've seen these workspaces happen in the past with builds that have "Execute >>> concurrent builds if necessary" checked. This is causing my build machine >>> to be loaded with 100s of git checkouts which is taking up a lot of space >>> and taking a lot of time to checkout builds. >>> >>> Thanks for any help! >>> >>> My Jenkins is 1.540. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to jenkinsci-use...@googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
