When the accurev plugin isn't using a workspace itself (i.e. the "use workspace" option isn't set), it uses "pop -v" to get the code from AccuRev.

If there happens to be an accurev workspace left lying around (quite likely, as you can't ever delete them) that happens to include the build's own workspace directory, then the AccuRev CLI fails (with an error "The -v option is not valid within a workspace."). This is a known limitation due to the way AccuRev behaves (AccuRev don't consider it a bug, they consider it "working as designed").

The plugin needs to use "accurev info" and grep for the line "Workspace/ref: (.)" and, if it matches, capture the workspace name (in \1) and then issue an "accurev chws" command to move the thing out of the way (e.g. to /tmp/processid/workspace-name) before continuing.

A workaround is to keep a look out for builds failing with this error and to log in and then manually issue an "accurev chws" command.