What's new in 2014.1

This section provides a summary of the notable changes in this guide for the 2014.1 release.

Major Changes

Triggers have been extended in the following ways:

  • The new trigger type command allows you to specify that triggers execute before or after the specified commands.

  • In addition to using trigger variables to support trigger/server communication, triggers can now use a dictionary of key/value pairs accessed via STDIN and STDOUT. The setting of the triggers.io configuration variable determines which method is used

  • You can now execute a trigger that is located in the depot.

  • Trigger variables have been added that allow you to access trigger definition fields, to determine what kind of server the trigger is running on, to return information about command execution, and so on.

For complete information, see “Triggers”.

Minor Changes

The current release of Perforce introduces a host of minor changes to improve performance and provide greater flexibility:

Display a history of checkpoint and journal activity for the server.

Use the new p4 journals command to display this information. For information, see “Checkpoint and journal history”

Rename a user.

The p4 renameuser command renames the specified user and modifies associated artifacts to reflect the change: the user record, groups that include the user, properties that apply to the user, and so on. For information, see “Renaming users”

Log out another user.

As a superuser, you can use the -a flag to the p4 logout command to log out another user. For information, see “Invalidating a user's ticket”

Synchronize your workspace with the depot using multiple threads to speed up file transfers.

You enable parallel processing by setting the net.parallel.max configuration variable to a value greater than one and by using the --parallel option to the p4 sync command. Parallel processing is most effective with long-haul, high latency networks or with other network configuration that prevents the use of available bandwidth with a single TCP flow. Parallel processing might also be appropriate when working with large compressed binary files, where the client must perform substantial work to decompress the file. For detailed information, see “Parallel processing”

Automatically append .gz extension to compressed checkpoint file

When you use the -z parameter with the -jd option, Perforce automatically adds the .gz extension to the checkpoint file. So, the command

p4d -jd -z myCheckpoint

creates two files: myCheckpoint.gz and myCheckpoint.md5.

Back up a workspace, label, or task stream.

You can use the -o flag to the p4 unload command to unload a client, label, or task stream to a flat file on the client rather than to a file in the unload depot. This can be useful for seeding a client into another database or for creating a private backup of the client. The flat file uses standard journal format. The client, label, or task stream remains fully loaded after the command is run.

Hide partial matches
Highlight matches
0 matching pages