Perforce Public Knowledge Base - New Helix Server Releases
Reset Search
 

 

Article

New Helix Server Releases

« Go Back

Information

 
Problem
What new features and functionality have been added in recent Helix Server releases?
Solution
Below are links to or details of what's new in recent Helix Server releases. 

 

2017.1

Helix Versioning Engine Administrator Guide: Fundamentals
Helix4Git
 

See the release notes for additional details.



2016.2

Helix Versioning Engine Administrator Guide: Fundamentals
Helix Versioning Engine Administrator Guide: Multi-site Deployment

See the release notes for additional details.
 



2016.1

Helix Versioning Engine Administrator Guide: Fundamentals
Helix Versioning Engine Administrator Guide: Multi-site Deployment
Using Helix For Distributed Versioning: DVCS

See the release notes for additional details.

 


2015.2

Helix Versioning Engine Administrator Guide: Fundamentals
Helix Versioning Engine Administrator Guide: Multi-site Deployment
Using Helix For Distributed Versioning: DVCS
 

See the release notes for additional details.

 
 

2015.1

Perforce Server Administrator's Guide: Fundamentals
Perforce Server Administrator's Guide: Multi-site Deployment

See the release notes for additional details.

 
   
 
Major new functionality in 2013.3:
NOTE: Restore from checkpoint required for upgrade
The new lockless read functionality can produce new log output.
 
See the release notes for additional details.
 

 


2013.2

Major new functionality in 2013.2:
Documentation change:
See the release notes for additional details. 
 

 

2013.1

Major new functionality in 2013.1 includes the following:

See the release notes for additional details.


    2012.2

    Major new functionality in 2012.2 includes the following:

    • New depot type of unload can be configured so that old or infrequently used clients or labels can now be unloaded. On large sites, reducing the working set of data, (particularly that stored in the db.have and db.labels tables) can significantly improve performance   
    See the release notes for additional details.


      2012.1

      Major new functionality in 2012.1 includes the following:

      See the release notes for additional details.



      2011.1

      Major new functionality in 2011.1 includes the following:

      • Support for streams. Streams simplify adoption of best practices for merging.
        The streams functionality is enabled with several new commands:
        • stream - Create or edit a stream specification
        • streams - Report on available stream depots
        • istat - Check for integrations needed for a stream
      • Two integration engines are supported with the 2011.1 server, including the new version 3 (v3) integration engine.

        With the v3 integrate engine enabled, p4 integrate provides improved base selection semantics and expanded resolve functionality, including resolving file types and file deletions. The new p4 merge and p4 copy commands use the new v3 integration engine.

      • The unlicensed (free) server version user/client limit has been raised from 2/5 to 20/20.

      See the release notes for additional details.



      2010.2

      Major new functionality in 2010.2 includes the following:
      • The P4AUTH and P4CHANGE server options are now fully supported
      • Replication enhancements to support depot file and server-to-server replication using p4 pull
      • New depot type archive can be configured and used to implement controlled transfer of revision content to archival storage
      • The p4 client and the C++ client API now support client protected regions through the use of the P4CLIENTPATH variable
      • The transfer of data between client and server is now verified against corruption. See lbr.verify.in and lbr.verify.out in the p4 configure command reference for additional details
      • New journal note record type, @nx@, now appears in journals and checkpoints
      • New internally generated counter lastCheckpointCompleted has been added along with a checkpoint MD5 digest that gets written upon checkpoint completion. See the p4 admin command reference for further details.
      • The change spec has a new Type field that can be used to specify a change as public or restricted. See the p4 change command reference for further details
      • New p4 copy command allows files to be copied (integrated) from one path to another based on file content differences rather than prior integration history.
      • Server configuration variables are now stored in the db.config table and may be displayed and set using the new p4 configure command
      See the release notes for additional details.
       
      Related Links

      Feedback

       

      Was this article helpful?


         

      Feedback

      Please tell us how we can make this article more useful.

      Characters Remaining: 255