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

CVS builds don't respond to updated module



    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • cvs-plugin
    • None
    • Platform: All, OS: All


      Changing the CVS module after a build occurs and having "Use Update" checked
      does not force a new checkout. It continues to do updates of the first module
      specified, not the module now specified.

      When this happens typically is when I setup a project to be a copy of another
      project using CVS module A. If I forget to modify the CVS module to module B,
      and proceed to do a build, it builds with module A. I fully expect that.
      However, when I fix the module to module B, it continues to build module A
      because it is simply doing a CVS update.

      Could an additional check be added to Hudson to check if the currently checked
      out code matches the module specified in the Job? If they don't match, then do a
      full new checkout.


        Issue Links


            bbrouwer Bruce Brouwer created issue -
            mc1arke Michael Clarke made changes -
            Field Original Value New Value
            Link This issue is duplicated by JENKINS-4489 [ JENKINS-4489 ]
            mc1arke Michael Clarke made changes -
            Assignee Michael Clarke [ mc1arke ]
            mc1arke Michael Clarke made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            mc1arke Michael Clarke made changes -
            Fix Version/s current [ 10162 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 132418 ] JNJira + In-Review [ 186535 ]


              mc1arke Michael Clarke
              bbrouwer Bruce Brouwer
              0 Vote for this issue
              0 Start watching this issue