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

CVS: First CVS Update after Checkout reads whole CVS-Repository

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • cvs-plugin
    • None
    • Tomcat6 / RHEL5

      When migration from old CVS-Plugin to the new Jenkins CVS-Plugin "Local Name" isn't defined.
      This leads to a HUGE problem: The first CVS-Update (not the first CVS-Checkout! This works!) will execute:
      "cvs update -d -P -r HEAD -D 2012-01-30 16:37:56CE"

      Thus the whole CVS repository is read.
      Simple solution: When migrating: "Remote Name" and "Local Name" must both be set.

            mc1arke Michael Clarke
            chrisabit chrisabit
            Votes:
            5 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: