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.