- Helix Core 2018.1March 2018
- Helix Core 2017.2October 2017
- Helix Core 2017.1May 2017
- Helix Core 2016.2November 2016
- Helix Core 2016.1July 2016
The 2018.1 release provides reliable and consistent replication of standby servers in a disaster recovery (DR) setup. Failover to a standby server in a DR scenario is significantly faster due to multiple steps being removed from the process via automation and a new replication method. This improved operational efficiency will result in reduced time and cost to recover service from a failure.
Admins can now hide the following sensitive server information from appearing within “p4 info”: server name, server address, server uptime, and server license IP address. For example, the license entry in “p4 info” will show “licensed” or “unlicensed.”
Improved Streams Usability
The 2018.1 release improves the usability of Streams by no longer requiring users to write long specs. Now, you can use wildcards to represent which folder and/or files are included in the path name of a Stream view.
Speed Up Remote Operations Even More with WAN Accelerators
The 2017.2 release allows you to use WAN acceleration technologies. WAN acceleration can be a great enhancement that dramatically increases the likelihood that remote sites are in sync at all times with central servers in a Perforce federated architecture deployment because the replication is quicker — even with extremely large files.
Boost Stability and Performance
Parallel sync operations are one of several techniques Perforce employs to make Helix Core the fastest VCS server on the planet. We’ve improved server resilience under load to support a greater number of simultaneous requests.
Faster File Transfers. Much Faster.
Transfer files over high latency networks up to 16 times faster than in 2016.2, even in federated deployments of Helix Core. See similar performance improvements for any communication between any server type — replicas, edge servers, commit servers, and proxies.
Support Git at Scale for Distributed Teams and CI
Helix Versioning Engine now supports Git at scale for distributed teams and multiple repos. Helix4Git speeds up builds by 40 to 80 percent and reduces storage by up to 18 percent with different mirroring options. For specifics, see Helix4Git.
Change Your File's Name or Location in a Single Command
Gone are the days when a “p4 move” command would require you to perform a “p4 edit” first. The 2017.1 release allows you to change the name or location of your files with a single command.
Identify and Sync Code Changes across Multiple DVCS Servers
Commands like “p4 files” and “p4 sync” now support using changelist identity so that it’s faster and easier to search, browse, and take actions on code changes that are shared across multiple Helix DVCS servers with different datasets.
Protect Your Servers from Outdated TLS Versions
Outdated cryptographic protocols compromise communications security over a computer network. This release enables greater flexibility to achieve tighter security by allowing admins to specify the minimum and maximum allowed TLS versions, preventing clients using other versions from connecting.
Submit Build Artifacts from Partitioned Clients
We gave you read-only clients, and you wanted more. We listened. Now you can submit build artifacts from partitioned clients to Helix while keeping new workspaces light and easily disposable for all your DevOps needs.
Turn Back Without Destroying History
Everybody makes mistakes. Easily undo an entire change list in a single operation, while retaining audit trails for enhanced security and compliance. Helix forgives, but doesn’t forget.
Expand your circle of trust and delegate permissions over a specific depot or path to a specific group or user so you don’t have to carry the weight of system administration on your shoulders.
What's New in Core 2016.1?
Increase Collaboration Efficiency Among Distributed Team Members
Speed up your DVCS collaboration workflow. Now you can work locally, propose a change, create a new shelf for it, and push it to a remote server for a quick review before submitting it to the mainline. It’s faster and takes up less space in storage.
Ditto Mapping for Greater Flexibility
Stop jumping through hoops to make workspace mapping comply with your needs. Ditto mapping grants programmers the freedom to work on blocks of complex code individually, working from shared libraries without months of build-failure frustration.
Customize Your P4 Aliases
Unleash your inner James Bond and give your most-used commands p4 aliases that make logical sense to you. Or, go into stealth mode and string several p4 commands together to trigger behind-the-scenes processes that simplify workflows.
Boost Automation with 'p4 reshelve'
Tool builders will love boosting automation in Helix with the p4 reshelve command.