What’s new in this guide

This section provides a summary with links to topics in this Guide. For a complete list of what's new in this release, see the Release Notes.

2019.1

• Carefully follow the steps at From 2013.3 or later to 2019.1 (distributed environment) or From 2013.3 or later to 2019.1 (single server) because they are different from previous upgrades.

• Extensions, a new technology that is similar to Triggers, but with advantages and additional capabilities. See Triggers and Extensions.
• When the server is busy with the maximum number of commands and therefore blocking standard users,the super and operator User types can still issue a subset of commands. See Limiting simultaneous connections > Too many commands.
• You can save disk space when creating an archive depot by using the option that includes lazy copies, which are small references to the location of potentially large files. A new database table, db.storage, replaces the db.archmap table to provide a link count for archive files on the server. This tracking reduces the complexity of identifying lazy-copies, allowing +Sn files to be lazy copied by reference instead of being duplicated with their full contents. See p4 archive -z inHelix Core P4 Command Reference.
• Faster verification of archives (depot files) with p4 verify
  • such verification can also be done with a new command, p4 storage -v
• Display, verify, or update physical archive storage with the new command, p4 storage
• Faster p4 obliterate
• The procedure for setting up a high availability server for Failover has changed. See A high availability standby within an existing installation should not be initially deployed as mandatory.
• Note that Helix Core P4 Command Reference indicates that the net.autotune configurable is on by default.
• (Doc-only change: The How protections are implemented topic has been expanded.)

2018.2

• Failover to a new master server is now an easier process

• Installation support for SUSE Linux Enterprise Server - see Linux package-based installation

• Clarification on when trigger-based authentication can fall back to a password request: Single sign-on and auth-check-sso triggers

• If you want to write a trigger that requires users to log in with additional security, see Triggering for multi-factor authentication (MFA)

• Multi-factor authentication (MFA) is the current name for a feature that was originally introduced as second-factor authentication (2fa)
• Helix SAML is a new feature for authentication

2018.1 patch

If you want to write a trigger that requires users to log in with additional security, see Triggering for multi-factor authentication (MFA)

Installation support for SUSE Linux Enterprise Server 11 and 12 - see Linux package-based installation

2018.1 release

You no longer need to use the -z option to restore a compressed checkpoint or journal. This allows the chaining of files for the restore. For example:

p4d -r . -jr checkpoint.42.gz journal.42 journal.43 journal

See the topic named "Database corruption, versioned files unaffected", which has a Note about Version 2018.1

See graph-push-reference triggers at Triggering with depots of type graph

A new structured log, ldapsync.csv, has been added to record the activity of p4 ldapsync. See Enabling structured logging.

2017.2 release

Triggers for external file transfer

See Triggers for external file transfer

Server background tasks

See p4 bgtask in the Command Reference

Parallel threads

p4 shelve now accepts the --parallel flag to specify that multiple files should be transferred in parallel, using independent network connections from automatically-invoked child processes. In addition, new configurables net.parallel.shelve.* allow p4 shelve to automatically use parallel threads to transfer files. Please see p4 help shelve and p4 help configurables for complete information.

The net.parallel.sync.svrthreads configurable reduces the number of parallel transmit threads used by sync commands when the total number of "user-transmit" threads (from all commands) running concurrently in the server would exceed the value of this configurable. Server monitoring must be enabled for this new configurable to take effect.