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

Changed CVS behaviour when "cvs update" and "cvs legacy mode" are selected

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: Linux

      When using multiple cvs modules in a single Hudson project, and setting both the
      "CVS update" and "CVS legacy mode" checkboxes in the project configuration,
      Hudson used to do the cvs update on each module. With the latest version 1.64,
      this behaviour has changed and Hudson now does the cvs update on the top level.

      Example:

      in the project config, enter the following module names as cvs modules to be
      checked out:

      products/Product1 products/Product2 products/Product3

      (We assume that the goal is to roll a releasable .tgz file that consists of
      several products configured for a specific customer)

      Hudson used to go into each module directory individually, doing the CVS update
      there. Now, it just does the cvs update in "products/" - which essentially tries
      to pull our entire CVS.

          [JENKINS-190] Changed CVS behaviour when "cvs update" and "cvs legacy mode" are selected

          Jesse Glick added a comment -

          Probably related to my change to automatically update modules that were checked
          out by a script. I don't think I foresaw that anyone was checking out secondary
          modules (as opposed to top-level modules). My fix cannot work for such cases, I
          think, but it could at least do what Hudson used to do in such cases.

          Jesse Glick added a comment - Probably related to my change to automatically update modules that were checked out by a script. I don't think I foresaw that anyone was checking out secondary modules (as opposed to top-level modules). My fix cannot work for such cases, I think, but it could at least do what Hudson used to do in such cases.

          Jesse Glick added a comment -

          Should be fixed in 1.65. Sorry about that.

          Checking in www/changelog.html;
          /shared/data/ccvs/repository/hudson/www/changelog.html,v <-- changelog.html
          new revision: 1.276; previous revision: 1.275
          done
          Checking in main/core/src/main/java/hudson/scm/CVSSCM.java;
          /shared/data/ccvs/repository/hudson/hudson/main/core/src/main/java/hudson/scm/CVSSCM.java,v
          <-- CVSSCM.java
          new revision: 1.11; previous revision: 1.10
          done

          Jesse Glick added a comment - Should be fixed in 1.65. Sorry about that. Checking in www/changelog.html; /shared/data/ccvs/repository/hudson/www/changelog.html,v <-- changelog.html new revision: 1.276; previous revision: 1.275 done Checking in main/core/src/main/java/hudson/scm/CVSSCM.java; /shared/data/ccvs/repository/hudson/hudson/main/core/src/main/java/hudson/scm/CVSSCM.java,v <-- CVSSCM.java new revision: 1.11; previous revision: 1.10 done

          blackmuzzle added a comment -

          Thanks a lot for the speedy response - I'll give it a whirl when the new version
          is out. For now we've disabled the "cvs update" thingy, and that works as usual
          (though it is slower of course)

          And yeah, our CVS structure is... not optimal. Alas it's the company's CVS and I
          cannot change that

          Anyways, kudos for the fast response!

          blackmuzzle added a comment - Thanks a lot for the speedy response - I'll give it a whirl when the new version is out. For now we've disabled the "cvs update" thingy, and that works as usual (though it is slower of course) And yeah, our CVS structure is... not optimal. Alas it's the company's CVS and I cannot change that Anyways, kudos for the fast response!

          Jesse Glick added a comment -

          Yes, please verify (or reopen) when 1.65 is out. Even better, verify on a
          development build before then - Kohsuke, is there a publicly accessible Hudson
          server for Hudson?

          Jesse Glick added a comment - Yes, please verify (or reopen) when 1.65 is out. Even better, verify on a development build before then - Kohsuke, is there a publicly accessible Hudson server for Hudson?

          Continuous build of Hudson is always available from
          https://hudson.dev.java.net/servlets/ProjectDocumentList?folderID=4939&expandFolder=4939&folderID=0

          One of my planned plugin is to look for changeset and update the affected issues
          to record which build contains what changes.

          Kohsuke Kawaguchi added a comment - Continuous build of Hudson is always available from https://hudson.dev.java.net/servlets/ProjectDocumentList?folderID=4939&expandFolder=4939&folderID=0 One of my planned plugin is to look for changeset and update the affected issues to record which build contains what changes.

          blackmuzzle added a comment -

          Verified Version 1.65, CVS update is working as expected again. Thanks for the
          prompt help!

          blackmuzzle added a comment - Verified Version 1.65, CVS update is working as expected again. Thanks for the prompt help!

            jglick Jesse Glick
            blackmuzzle blackmuzzle
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: