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

CVS builds don't respond to updated module

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • cvs-plugin
    • None
    • Platform: All, OS: All

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: