The plugin adds its configuration settings panel to the runner settings page: choose Swabra mode as before or after build.
If you choose
After build mode build files cleanup will be performed after the build. Between builds there will be clean copy in the checkout directory which gives possibility to free more disk space.
If you choose
Before next build mode previous build files cleanup will be performed at build start. You only need to use this mode if files are required between builds or for debugging.
Strict mode option to enable Swabra "strict" mode. The build will fail if at the start there are any files which were created during previous build.Specify
When performing files deletion on Windows agents Swabra may come across files and folders which are locked by some outside processes.
If you check the
Determine file locking processes on Windows agents option the plugin will attempt to kill these processes and finally remove files (in
Strict mode) or just report (in normal mode) these processes.
If this option is unchecked list of newly created during the build files, which swabra failed to delete will appear in the build log.
Locking processes detection can also be turned on when build files cleanup is disabled. In such case useful information about locking processes (or their absence) will appear in the build log.
To enable locking processes detection you also have to specify
Handle.exe path - path to Handle excutable on Windows agent. If specified will be used to determine processes which hold files in the ckeckout directory. You may also use
handle.exe.path system property on agent to pass this path to the plugin.
If at the specified path there is no handle.exe found the plugin will try to automatically download this executable (unless
swabra.handle.disable.download system property is set).