-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
Windows/Linux
Workspace is inconsistent with configuration. Scheduling a new build: No CVS dir in C:\Program Files (x86)\Jenkins\workspace\Common Done. Took 0 ms Changes found
Jenkins is looking for a "CVS" directory in the workspace. Since it does not find this (it is not supposed to - multiple modules/legacy option checked), it tries another build, and another and another and so on.
In the example above, "C:\Program Files (x86)\Jenkins\workspace\Common" is the path to the workspace, and contains other folders that are the actual modules for the build:
C:\Program Files (x86)\Jenkins\workspace\Common\libAlpha
C:\Program Files (x86)\Jenkins\workspace\Common\libMath
C:\Program Files (x86)\Jenkins\workspace\Common\commonLib
C:\Program Files (x86)\Jenkins\workspace\Common\mainApp
This is also on an issue on linux slaves, without spaces in the path.