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

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

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

blackmuzzle
https://hudson.dev.java.net/issues/show_bug.cgi?id=190
                 Issue #|190
                 Summary|Changed CVS behaviour when "cvs update" and "cvs legac
                        |y mode" are selected
               Component|hudson
                 Version|current
                Platform|All
              OS/Version|Linux
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|www
             Assigned to|issues@hudson
             Reported by|blackmuzzle






------- Additional comments from [hidden email] Thu Dec  7 12:52:02 +0000 2006 -------
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.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]