Swarm 2015.2 Guide (August 2015)

Comments are now editable. If you are logged in, and the author of a comment, you now see an Edit link in the comment's footer. Clicking this link allows you to edit the comment text, remove selected attachments or add new ones.

See Comments for details.

These localizations do not ship with the publicly released Swarm, but are available through Perforce's region-specific resellers.

Swarm now includes a trigger script written in Perl. The new trigger is compatible with the existing Bash trigger. The new trigger adds support for using Swarm with a Perforce service configured using the commit-edge architecture, and also fixes a bug with strict enforcement mode and +k file types.

Support for multi-site deployments utilizing the commit-edge architecture is now included in Swarm. Use of the new Perl trigger to required for Swarm installations connecting to a Perforce service configured using the commit-edge architecture.

See Setup Swarm triggers with a Linux-hosted Perforce service and Trigger options for details.

The Subject: line of notifications for submitted changes has been revised from Change @54321 to Commit @54321.

Swarm now applies Perforce proxy rules during emulation of IP protections. Previously, proxy rules were not taken into account. Now, Swarm now applies proxy rules as an intermediary according to the user's IP address.

See IP address-based protections emulation for details.

Two options have been added to limit project configuration changes to users with admin privileges:

See Projects for details.

With the new Perl trigger, two options have been added to exempt changelists from strict or enforce verifications by file count and file types.

See Trigger options for details.

Moderators now receive email notifications for commits and reviews for the branches they moderate, even if they are not members of the associated projects.

See Notifications for details.

The login page now includes a nice background image. See Log in / Log out for an example.

The button for editing a project's settings has moved into the project's toolbar, and while editing a project, the toolbar and sidebar now appear.

Swarm now generates host-unlocked tickets on login. This is needed to integrate with other Perforce services like p4-search.

When using line hash handling (e.g. #l123, the targeted line is now positioned 1/4 of the browser height from the top. Previously, it was positioned at 100px from the top.

A performance problem that could occur with large numbers of users, groups, and projects has been fixed. With 5,000 users, 5,000 groups, and 500 projects, load times for the project listing have been reduced by more than twenty times.

The email notifications template has been simplified by removing the grey border and reducing the margins.

The History tab has been renamed to Commits. See Commits for details.

Comment counts for reviews and jobs now reflect the number of open (non-archived) comments. Hovering over the number of comments shows the number of archived comments. Previously, only the total number of comments was shown.

The visibility of the Show More Context rows in diffs has been improved. See Diffs for details.

An option has been added to prevent authors from approving their own reviews, even if they are a moderator or user with admin privileges.

See Disable self-approval of reviews by authors for details.

The Imagick module now converts .tif files for display. Previously, only the .tiff filename extension was recognized.

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.

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.