Skip to main content
TrustRadius
Perforce Helix Core

Perforce Helix Core

Overview

What is Perforce Helix Core?

Multinational company Perforce, headquartered in Alameda, California offers a version control and peer code review solution. Perforce version control is built around Helix Core with add-on products for code review (Helix Swarm) for free, and add Git support products (Helix4Git…

Read more
Recent Reviews

TrustRadius Insights

Users have adopted various revision control packages like Perforce, Git, and SVN to develop and store data independently. Perforce serves …
Continue reading

Great Once It Is Set up

10 out of 10
March 14, 2020
Incentivized
Each lab site has its own set of developers that operates independently but we are moving towards more collaboration and sharing software …
Continue reading
Read all reviews

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Perforce Helix Core?

Multinational company Perforce, headquartered in Alameda, California offers a version control and peer code review solution. Perforce version control is built around Helix Core with add-on products for code review (Helix Swarm) for free, and add Git support products (Helix4Git and Helix TeamHub).…

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

258 people also want pricing

Alternatives Pricing

What is GitHub?

GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans…

What is GitLab?

GitLab DevSecOps platform enables software innovation by aiming to empower development, security, and operations teams to build better software, faster. With GitLab, teams can create, deliver, and manage code quickly and continuously instead of managing disparate tools and scripts. GitLab helps…

Return to navigation

Product Details

What is Perforce Helix Core?

Perforce Helix Core is a version control system for teams who need to accelerate innovation at scale. It is used to store and track changes to digital assets, from source code to binary to IPs, and connects teams.

Perforce Helix Core Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

Multinational company Perforce, headquartered in Alameda, California offers a version control and peer code review solution. Perforce version control is built around Helix Core with add-on products for code review (Helix Swarm) for free, and add Git support products (Helix4Git and Helix TeamHub). The original Perforce SCM solution was expanded via the Surround SCM, a software configuration management application which was developed by Seapine Software and now owned by Perforce since that company's acquisition of Seapine in October 2016. Perforce integrated the software with its Helix ALM product. Surround SCM integrates with Perforce's Helix ALM to help manage code, along with requirements, tests, and issues.

Reviewers rate Support Rating highest, with a score of 9.6.

The most common users of Perforce Helix Core are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(32)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Users have adopted various revision control packages like Perforce, Git, and SVN to develop and store data independently. Perforce serves as the backbone of version control for builds, ensuring everyone has the latest content and code. It is easy to get started with Perforce, allowing users to pull the files they want. However, it can be challenging to perform more complex tasks like branching and integrating. Nevertheless, Perforce supports a rich GUI for most tasks and a command-line interface for automated or advanced tasks, making it suitable for users with varying technical proficiency.

Perforce is accessible globally and externally to product licensees, supporting all major features like branching, shelving, and p4web. The visual client of Perforce is user-friendly, presenting the directory structure conveniently and consistently across platforms. Its merge optimization feature is highly useful for day-to-day operations, providing efficient code merging capabilities. This makes Perforce ideal for agile development, big data services, and marketing materials across thousands of automotive dealerships.

Moreover, Perforce is scalable and suitable for small to enterprise-level projects. It integrates well within a .Net environment and is leveraged by several departments to track changes in software, documentation, and assets, providing quick access to change history and approvals. In industries like healthcare, Perforce Helix Core serves as the source control management system of choice for corporate products, internal applications, custom code, and configurations. Beyond version control purposes, Perforce is also used for collaboration and sharing software between independent developer groups within and across different lab sites. In addition to its version control capabilities, Perforce ensures the integrity of code bases by providing backup and revision control features.

Attribute Ratings

Reviews

(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Score 4 out of 10
Vetted Review
Verified User
Incentivized
As the primary tool for version control across our organization, Perforce provides an enterprise level solution for the management of our various products and software branches, among other things. Perforce branching, action triggers, locking, and other features make it ideal for the type of work historically done by CDK Global (formerly ADP Dealer Services). It supports the production of highly scalable big data services, agile development of websites and other marketing materials spanning thousands of automotive dealerships, and much more.
  • The branching mechanisms in Perforce allow for an enormous codebase to be duplicated into release versions weekly with little impact upon things such as the speed of queries against the version control.
  • Action triggers permit such things as automated builds of software versions, dynamic messaging when issues are identified either within or prior to a build process, and much more.
  • Locking provides the ability to prevent modifications of stable, tested versions in order to ensure validity when they are released.
  • As new tools like Git enter the market, enterprise solutions like Perforce are often seen as rigid and overly complex.
  • Occasionally, the branching system in Perforce seems to fail to retain proper branching history, making it difficult to track the original source of changes if they were initiated across multiple branching operations.
  • When a change made has inadvertently caused side effects, it can be necessary to back out code changes. This process is difficult to do when the changes needing back-out are spread across multiple changelists for the same set of files. It can be even more difficult if any of those changelists contain files that should not be backed out, though this latter point partly indicates a flaw in the developer's process.
For large-scale codebases with fixed and regular releases that do not follow a continuous delivery paradigm, Perforce is certainly well suited. In projects that are small and distinctly separated from other discrete (though potentially dependent) units, the benefits of the Perforce tool may not be as clear of a victor over other systems.
  • In the case of CDK Global, Perforce has done an excellent job of maintaining service levels for clients. This is not in terms of customer service, as much as the operational stability of the marketing materials (websites, services, etc) that are in place as a result of the assets held in Perforce version control.
  • Apache Subversion,Git
Subversion
  • missing many of the features that Perforce provides, but
  • a much more lightweight versioning system
  • with fewer commands, this has a lower barrier to entry
  • like Perforce, has a single, centralized database master
Git
  • similarly has a more limited feature set
  • excels in the realm of rapidly creating and merging feature branches
  • has a concept of origins, but each client has its own full-fledged repository
The difference between Git and Perforce related to centralization is of great interest. This simplifies working on teams that are geographically disparate, whether separated by a few miles or on different sides of the planet (such as the United States West coast and India).

Having a centralized repository in this case would vastly slow down the request/response cycle for repository access, whereas a replicated system like Git keeps the process fast until the developer needs to push to or pull from the origin. Each client also can define its own origin in Git, such that a daisy chain from a given individual to a source of record (or multiple as a form of fallback mechanism) can vastly improve efficiency.
7
The features we have come to rely upon, in combination with the vast history that has already been stored in the Perforce system, will more than likely persist our use of the tool moving forward. Ultimately, however, this is a decision for other members of our team to make for the organization.
This rating is related to setting up an environment from an existing Perforce repository. Initial setup of Perforce as the repository for the company was done by a separate team long prior to my inception.
Return to navigation