This section concerns only the latest version of the plugin. You are welcome to download it directly from public TeamCity server.
Plugin adds support for cleaning new files created during the build. The files modified or deleted during the build are also reported in the build log (but are not affected by the plugin).
The plugin remembers the state of the file tree after the sources checkout and on next build start deletes all the newly added files.
The plugin also gives the ability to dump processes which lock the checkout directory before build finish (requires handle.exe)
In final stage of development. Snapshot builds are available.
Everyone is encouraged to try the plugin.
The current plugin version is designed to work with TeamCity 5.1, TeamCity 5.0.x and TeamCity 4.5.x (there are three plugin configurations).
Directly from public TeamCity server:
5.x last nightly build
5.0.x last nightly build
4.5.x last nightly build
<TeamCity Data Directory>/pluginsfolder.
The plugin can be used with any runner. Swabra tab provides UI options to enable scanning checkout directory for newly created, modified and deleted files and for enabling file locking processes detection.
Checkout directory state is saved into a file in the caches directory named
<checkout_directory_name_hash>.snapshot using DiskDir format. Checkout directory to snapshot name map is saved into snapshot.map file. The snapshot is used later (at the start of the next build) to determine which files and folders are newly created, modified or deleted. It is done by actual files' presence, last modification data and size comparison with corresponding records in the snapshot.
The plugin adds its configuration settings panel to the runner settings page.
Perform build files cleanup option to enable build files cleanup.
Ensure clean checkout directory to ensure that the checkout directory corresponds to the sources in the repository at the build start. If detecting any modified or deleted files in the checkout directory before the build start Swabra will enforce clean checkout. The build will also fail if some newly created during previous build files can't be deleted.
Ensure clean checkout directory you will only get warnings about modified and deleted files.
Cleanup rules setting to specify newline or comma delimited set of
These rules tell Swabra what files and folders should be involved in files collection process.
-: prefix is specified rule as treated as include.
A path can be checkout directory relative path or a mask with ant-style wild cards.
By default all paths are included.
Ignoring a directory leads to ignoring the whole it's content.
Rules on any path should come in order from more abstract to more concrete, e.g. use
-:**/dir/** to exclude all
dir folders and their content,
-:some/dir, +:some/dir/inner to exclude
some/dir folder and all it's content except
inner subfolder and it's content.
Note that after removing some exclude rules it's advisable to run clean checkout.
Locking processes setting to inspect the checkout directory for processes locking files in this directory.
Kill options to get report about such processes in the build log or kill them.
Note that for locking processes detection handle.exe is required on agents. Click the
Download handle.exe link for downloading.
Verbose output option to enable detailed logging to build log.
If the build is set up to checkout on agent swabra by default ignores all
CVS folders and their content.
To turn off this behaviour specify empty swabra.ignored.paths system.property.
URL for downloading Handle.zip, press
Download button and TeamCity will automatically download Handle, extract and send to Windows agents.
handle.exe will be present on agents only after the upgrade process.
Note that you need to have enough permissions to start the download.
You may also download Handle, extract it on agent and set up the
handle.exe.path system property manually.
Generally snapshot file is deleted after files collection. Set
swabra.preserve.snapshot system property to preserve snapshots for debug purposes.
h3. Known Issues
If you believe you've faced a bug: Issue Tracker (project: TeamCity)
If you want to ask a question or discuss: Forum
Sources in JetBrains Subversion repository.
Builds for TeamCity 5.x and
Builds for TeamCity 5.0.x and
Builds for TeamCity 4.5.x at JetBrains public TeamCity
Issue in TeamCity tracker.