On Wed, Jul 27, 2011 at 12:16 AM, Benson Margulies <[email protected]> wrote: > I fixed this by changing the workspace path for the -m2 job. I turned > out to have karma.
Could we please change these builds not to use custom workspaces at all? Right now, files ends up where we do not want them on the slaves. If a custom workspace is really needed, the first part of it's path must be "workspace/<job name>/". I don't want to break the build, so please fix this yourself. If not, I'll remove the custom workspace setting in a few days. /niklas
