Swarm 2015.1: User Guide (May 2015)

User-facing strings now run through a translation component that supports string replacement, escapement, and pluralization. The default locale, and a fallback locale, can be set in the configuration file. The browser's locale is detected automatically, although this can be disabled.

See Locale for details.

Files and folders can now be downloaded as ZIP archives. Any depot path can be archived, however it must not be larger than 512mb (the default limit).

See Downloading files as ZIP archive and Archives configuration for details.

Swarm now limits the number of files displayed in a changelist. Previously, if you viewed a particularly large change with many thousands of files, Swarm might run out of memory. Swarm now limits the number of files displayed to 1,000 (by default), and the limit is configurable.

See Changelist files limit for details.

Swarm now detects JIRA issues that are wrapped in round brackets "()", and curly braces "{}".

The XHProf module now automatically cleans up old report files. Previously, if XHProf was enabled the number of log files would grow over time, and due to their large size consume a significant amount of disk space.

A configurable timeout now controls how long Swarm can spend submitting files to a Perforce service.

See Commit timeout for details.

Swarm now detects errors connecting to a Perforce service and reports them as HTTP 503 errors (service unavailable). This improvement should assist in debugging problems with the port, user, and password configuration.

User avatars now appear rounded. Rows in tables no longer appear with alternating background colors (zebra striping).

A notice has been added to the top of the Swarm home page when Swarm detects that no workers are running. This helps highlight a common configuration problem.

The rules governing review state transitions have been improved to allow review authors to approve or reject their own reviews if they are a branch moderator.

See State change restrictions with moderation for details.

Swarm maintains a variety of information in the Perforce service's keys facility. By default, users with list-level privileges can read these keys, which can include comments that contain excerpts of code they may not normally have access to.

Perforce server version 2013.1 and higher have a configuration setting to require admin-level privileges. See Hiding Swarm storage from regular users.

Swarm must be installed to the root of a domain. We recommend creating a virtual host dedicated to Swarm.

Due to issues with LibreOffice's headless mode on the Mac platform, Swarm cannot display Office-type file formats if it is installed on the Mac platform.

Pre-commit reviews in a task stream are not yet supported.

We include a trigger script for both Linux/Mac and Windows; however, the Windows variant currently lacks support for the following features:

The Swarm trigger scripts (found in p4-bin/scripts) document the trigger table entries to add, making use of %quote% to surround the pathname to the script; however, %quote% is not supported on 2010.2 Perforce Servers (they are harmless though). If you're running a 2010.2 Perforce server, ensure that there are no spaces in the path to the trigger script.

Reviews that involve KText files are not currently compatible with the strict trigger as the keywords make the review's files appear to be modified even when they are unchanged.

Upgrades from 2014.2 RPM packages are incorrectly treated as new installations by the packaging system. This is due to the package being renamed in 2014.3. Minor configuration issues might result.

Multiple issues prevent Swarm RPM packages from installing correctly on RedHat Enterprise Linux, or CentOS, versions 7.0 or higher.