By default, this plugin checks out the latest changes without using a workspace. This removes the need to manually create a workspace for each project, and removes the need for the plugin to make transactions while moving the workspace from slave to slave as the build migrates from slave to slave.

However, there may be situations when the use of a workspace is preferred. If you want to use a workspace, select this option and enter the name of an existing workspace in the Workspace field. The plugin can manage migrating the workspace to the appropriate build machine and re-parenting the workspace to use the correct parent stream (Jenkins considers the Stream field value as the parent stream). Note that workspace changes (accurev chws) are logged as AccuRev transactions.

When not using a workspace, the following AccuRev commands will be used:

When using a workspace, the following AccuRev commands are used:

If the workspace needs to be relocated or if the host machine needs to be updated, the following AccuRev commands are also used:

Otherwise, the following commands are run:

Note: If you decide to stop using an AccuRev workspace after having run a build, you must manually move the AccuRev workspace directory.