Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14551

an update which contains added files merged from a branch results in those files having doubled content

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • subversion-plugin
    • None
    • sles 11, Jenkins 1.470, subversion server is CollabNet Subversion Edge 1.3.1

      Using the "Emulate clean checkout by first deleting unversioned/ignored files, then 'svn update'" svn strategy, we recently had a branch merged into
      trunk that added some files. When the Jenkins jobs configured as above
      ran against trunk, those added files had their content duplicated.

      A quick google suggested it has happened before:

      http://grokbase.com/p/lucene/dev/126m8fpw9q/jenkins-lucene-solr-tests-only-4-x-build-137-still-failing

            Unassigned Unassigned
            cjw296 Chris Withers
            Votes:
            34 Vote for this issue
            Watchers:
            36 Start watching this issue

              Created:
              Updated:
              Resolved: