Helix Core Reviews

User friendly graphical tools like the Revision Graph and file history graphs.

Securely manageable single repository as well as large repositories that delivers files quickly to distributed teams.

Efficient and effect support.

I think using the graphical interface to perforce (p4v) is a more effective way to work with perforce for most users. It makes it much easier to manage multiple workspaces, change lists, branch mappings, merging and most other functions.

Time lapse tool is just fantastic

I can not live without side-by-side diff tool at a mouse click

Command line tools are powerful but needs little more experience, that comes with time.

Applying the scripts is making daily work easy.

nitial learning is slightly rough when you come from GIT background, as you pick it up, it becomes fun. I watched online videos from basic to advanced level and now I am comfortable using it. Everyday there is something I learn from my coworkers.

Setting up Helix server is rigorous at the first go, but if you it once, then next time it is straight forward.

User-friendly

scalable

easily manageable

Good for large distributed teams

Merging and branching a piece of cake

File history easy to access

fast source code access in agile environments where each branch exists for short time period as we prefer to branch out, implement the functionality and then merge it back to main. We prefer short lived branches and frequent mergers than long waited mergers.

There are excellent graphical tools like the Revision Graph and the Merge Tool included.

The possibility to automate and access by scripts using command line and various API's is very useful.

There is very good support and knowledge base available.

The Swarm add-on to Perfore is exellent for collaboration and reviews but it actually should be even more tightly integrated as part of the basic product rater than an add-on.

Perforce is very good at handling large files and large repos efficiently.

The concept of a workspace and checking out files is non-intuitive and confusing to new users who are used to Git.

The convienient way of doing Rollback/Backout is good but it is very problematic when it comes to integration records (merges).

Server administration and setup gets a bit complicated when you need more advanced features like replication, broker, SSL-support.

You need to take the time to understand the concepts and the features as traditional Perforce differs from Git.

Versioning of various types of development artifacts - all types of data.

Graph and History give a very interesting visual information about source changes.

Customisation via scripts at submit or via P4Broker make the tool very flexible.

Merge tool is good visually and it works well to integrate changes from multiple branches, it is very functional.

Integration with Visual Studio IDE, SlickEdit, and other programming IDE is good.

Labels are too easy to change, it cannot be used to identify official release for us.

The fact that directory are not a controlled object in Helix (at least when not using Streams) force us to create dummy files to introduce file architecture for a project.

It would also be good support directory link, like Linux system (this is maybe possible with Workspace views but it was not that easy or even not functionning for our projects.

Very interesting tool for multiple OS platforms. Good visual interface and command-line interface (plus API's to Python, C/C++). This tool can be extended quite easily to enforce our processes within the whole developpement teams.

Good collaboration among team members and track all changes to our code.

Il also allows us to perform efficient code reviews by shelving files with changes, without disturbing other developpers working in our branch.

Reconciling changes made locally during customer site-support is very good to keep all changes performed away from the office and submitting the changes once returning from these interventions.

Consistent across all business units and developers. It keeps improving in ease of use and performance.

It is expensive, and not particularly easy to work with. It does not tie in well to our BOM system.

Now comes with Git compatibility, so one interface is needed. It will handle multiple nested projects well, and is used for all of our documentation needs. It does need a "champion" or administrator willing to put in the time to learn.

Coordinating VCS between 50 software developers, and sharing updates to libraries. The learning curve is small for simple things like checkin and checkout, but branch and merge have to be done carefully.

Perforce (Helix) is one of the best source control providers for medium to large projects and companies, especially those who need tight security. Their product suite has expanded to cover other needs like code inspections and git services which make it a more complete solution.. Many top tier companies rely on it, The ability to handle very large files is a must for us. They offer a free tier for up to 5 users which is a great way to get started. Every time i have dealt with support they have been fast, efficient and often local. They are not afraid to reinvent themselves which in this market with competitors such as git and microsoft team services is a must. They also offer service licences which is good to not have to use admin accounts for core services.

While they offer the main perforce server on windows, other services must be deployed to Linux machines such as gitfusion. Setting up some of these services require a lot of experience and I had to have a few support calls (which were some of the best I've had and local to my country Australia) to get going.

Try out the free tier to see if it meets your business needs.

We are using perforce for source control management storing code, documents and binaries. We also use Swarm to manage our source code reviewing process. We were able to consolidate and move away from multiple vendors like our previous Code Collaborator program. We have dabbled in using their git solution for a few of our smaller projects.

Helix is a state of the art tool which allows a lot of flexibility and is very fast. Many of the recent releases put out by Perforce Software, the maker of Helix, have given it similar capabilities to Git: distributed VCS aspects, the ability of using a Git client through Git Fusion, or the ability to connect it to GitLab, a solution similar to GitHub or BitBucket.

The level of support offered with a Helix license is unparalleled. Bugs are fixed in a timely fashion and each major release brings about many exciting new features.

The initial learning curve is a tiny bit steeper than some of the other version control solutions. The concept of workspaces takes a little effort to fully understand, but it is workspaces which also make Helix more flexible than some of the other solutions out there.

Safeguarding of intellectual property while providing fast source code access in agile environments.

The visual interface is mostly intuitive. I think they are still working to bring the visual client in line with the server product's feature set so I expect things to improve as time goes on. They have made large changes to their offerings and while it's taking a bit to get things sorted it seems like they are heading in a good direction. Visual interface has a plethora of tools to visualize the changes in your code lines to see what has changed and when and by whom.

Perforce Support has been really good and helpful in resolving issues we've encountered as well as helping me get up to speed on administering their product.

The visual client seems to have multiple ways to accomplish certain things which leads to confusion as to which is the correct way to go about things. Not everything is intuitive and I've found myself digging on more than one occasion at first for how to do something. Once you're situated though it's not so bad and things are pretty simple to operate.

Getting out of ClearCases managed network filesystems which gave us very slow performance for our developers. Perforce is much faster because it stores things locally in a workspace. It allows easy importing of other modules into your code line as well.

Perforce is an incredibly powerful and flexible centralized source control management system whose support is second to none (not that you'll need it that often). Their development teams are always improving the existing core of the tool in addition to adding new features and support for elements such as security, distributed SCM, and many others. Surrounding the main Helix software are a plethora of equally well developed and maintained satellite services such as Git support (GitSwarm), team collaboration (Swarm), visual merge tools (p4 merge), etc. As to their reliability and scalability, you need only look to the companies who have trusted their source to Perforce to understand its capabilities in this arena, and I will mention again the first rate support you receive with the tool, I have experienced none better. Perforce is extremely stable tool as well, and once it is set up and running as required, it will faithfully continue to run without any fuss or muss.

As the sole (part time) admin of an 834 user system I have found myself wanting for greater granularity in the delegation of certain administrative functionality to trusted development team leaders. Perforce is adding these functions as the tool moves forward (currently running server version 2015.2 as of this writing) which will help me with this, but as of right now, this is a small pain point for me. Another difficulty that can be experienced, especially if migrating from a non-branch based SCM tool, is the learning curve for the use of client workspaces and proper branch policy. This is not an issue with the Perforce service itself, but it is a more powerful (and hence more complicated in some aspects) tool which may require more effort in initial training with the tool and its concepts. Well worth the effort however.

If you are looking for an enterprise grade, highly scalable and expertly supported centralized source control management tool, Perforce is the best there is. If decentralized SCM is preferable or then Git is a great option as well, but know that Perforce also support DSCM capabilities as well, along with excellent integration with Git repositories, again with excellent support.

We migrated off of Microsoft Visual SourceSafe in order to make user of the concurrent checkout and branching abilities of Perforce. This was back in 2007. The benefits however extended far beyond the core benefits that the system provided us. Whereas in VSS most development was performed against the main trunk of development (development occurred on mainline in Perforce parlance), we could begin to practice stable mainline procedures within Perforce where development would take place in development branches and once vetted through a build and QA system, promoted to mainline once deemed stable. The "copy up, merge down" process allowed us to further ensure the integrity of our mainline and allowed for development branches to catch up with mainline when it changed.

We have not implemented Streams because they do not currently fit into our use of the system, but provide yet more ability to enforce process on the movement of code and maintaining the correct hierarchy of codelines.

The various tools that come with Perforce out of the box such as the Merge tool, Revision graphing, stream graphing, distributed source control, Time Lapse Vies, etc are also a boon for developers as it allows them to track down where modifications to a file were received from, and by whom.

It has also allowed us to improve our resilience through the use of replication servers, proxies, and in the future Edge servers (where remote sites can hold their own set of metadata [database] files while still syncing source to the primary server). Our checkpoints can happen nightly against the replica server, leaving the master server online to continue to serve users non-stop.

And of course, I'll mention for a third time the Support team at Perforce, which is absolutely fantastic.

My favorite aspect is the ability to interact with 3rd party software or even with our own in-house-built applications. Additionally, the ability to use it at my own home-owned server to test various aspects is just fun to do.

Honestly, there are a few small things that annoy me about the product, but they are so easily worked around that I can't even remember what they are.

Out of the box, it's incredibly easy to use. It integrates well with a lot of other products that you may not even know exist, and it's easy to use for everyone involved, from the admin to the end-user.

We have been able to create our own way to deploy fixes to customer sites by using changelists. We can create release notes from the changelist descriptions (with filters to determine what is only meant to be seen by customers), and it's been an easy process to accomplish this.

Perforce Helix is a very fast and reliable source control engine. It's client tools are easy to use and provide great visualizations of file and branch differences. Time lapse view is a very useful way to see the evolution of one files changes. Managing branches with a streams depot is easy and makes enforcing a branching methodology simple.

Some of the concepts surrounding merging between branches can be a tricky to explain to all users.

Merging changelists between branches where files have been moved, renamed or deleted can be a bit tricky with obscure error messages. Better guidance on how to resolve these issues when they occur would be appreciated.

A fast and reliable source control system. P4V, the dekstop client for Perforce is easy to use for most operations, and its integration with Visual Studio is excellent.

1. You can use Helix VCS as is for keeping version control of software. You can also use the Helix VCS server by installing a middle-ware, which gives you the capability of git command line to access the repository.

2. We also used the "Forwarding Replica Servers" for distributed sites. If you use ClearCase Multi-sites, you will realize that the designed from Helix VCS is maintenance free. You only need to setup it up once and you're done. As for ClearCase Multi-sites, you are required to learn how to use the ClearCase Mastership.

3. The final thing I want to mention is the support from Helix VCS support team is second to none. Making a great product and the support team is paramount in a "Mission Critical Application" in the software industry.

There is a learning a learning curve on how to manage git server using Helix CVS.

Once you learn how it operates, it works as advertised.

Yes.

We can use Helix CVS to keep our version control of the software.

If we want to use Git, it is possible without changing the backend.

Ease of Multiple sites development setup

Lower maintenance cost.

Easy to maintain.

The Helix ecosystem of products (server and clients) is mature and stable and because of its paradigm of not tracking local file edits it is fast. The GUI clients make it easy for a wide variety of users (in our case, engineers, artists, game designers and sound designers) to understand source control.

The APIs and triggers on submits allow sophisticated tools to be built to streamline the development process.

The 24/7 response team always quickly answers queries.

The Helix Swarm tool is great for code reviews.

The free 20 user option allows you to try it out though it does take some effort to set the server up well.

My main issue with Helix as that the clients are not updated very often and a number of issues with the user interface have remained unaddressed for years. Also the MacOS client is much less stable than the Windows client.

In our particular use case where we use Unity the integration between Perforce and Unity is still in need of further work though it is useable.

We are building graphically rich video games which requires a team of many disciplines with differing levels of technical expertise and for the vast majority of users Helix's user interface does make it easy to work with source control.

Game development also involves the creation and management of a lot of digital assets and Helix's storage scheme does store them efficiently and deliver new changes to a distributed team quickly.

Game development is increasingly about building and maintaining a great live service with frequent updates to the game and Helix helps support this by allowing updates to be developed in different streams with different release dates.

It integrates fairly well with MadCap Flare, allowing us to keep a version history of documents that we create so we can roll back if necessary. It is easy to use once you know the layout, and the check-in/check-out system is great for version control.

I also like that the desktop client lets you see your full file directory and open files from there in different programs.

By default, you are allowed to check out and make changes to a file that someone else has checked out. If you don't know this and don't have exclusive checkout enabled, it's possible to lose changes that you make

We primarly use Perforce for version control and history. We need to make sure that multiple people have access to the same files, but all changes are tracked and saved and no one loses their changes because two people were editing a file at the same time

Perforce is feature full and allows us to do pretty much what we want to do. It helps with our productivity and to manage the data of our large scale productions.

I like the UI tool (P4V) but also a the command line tool option which we use extensively in our continuous integration system.

The new Helix4Git is also a new and interesting feature within Helix Core.

Easy to administer user and group rights.

There is a little bit of a learning curve when new people join our teams and they do not have Perforce knowledge. It is somewhat different from other version control systems like Git.

Not worth it if you have a smaller team with smaller projects, something like GitLab would be more suitable..

Large-scale production repositories with a lot of data and big files.

I like perforce as the best versioning tool I have used so far in my 12 years of career in software engineering. If u r looking for client-server model versioning engineer perforce is the best solution u can get. now they have updated with git clients and perforce server which is closing the gap between distributed and client-server model of versioning.

not having the facility of creating personal branches and tracking versions for them

its a good tool if u r considering client server versioning model

our source code repo is in perforce wihch enables us to track the code changes across the sites and able to build it with full control on whats, which and when it is build

1) It's so easy to learn, even artists, writers, and other "less-technical" users can get it right away; 2) It's FAST; 3) It's a very, very strong product, best I've ever tried; 4) It scales really well. One depot can handle ALL of your needs; can handle file-sizes and types that Git can only dream about; 5) The Perforce Support organization is THE BEST; 6) Free for up to 20 users; 7) up-and-running in minutes; 8) DVCS option; 9) Support. And FAST; 10) Did I mention it's FAST? And no one does Support better; 11) Their Support is FAST, too.

They need to do a better job of letting people know how great their product is. Seriously, more people need to use it. It lets us develop better software, faster.

Up until recently, it used to be very easy to find older versions of the product. This could be pretty useful. Currently, it's much harder to find the older versions. I get that this is what companies do, and I understand that they might not want to *support* older versions, but it's really a nice thing to have if I want to do some testing.

Take it for a test drive. Talk to Support. It's free for up to 5 users, so give it a whirl. Used to be 20, which I preferred. I think they'd be better off giving it away for free and just charging for their excellent Support.

Its spectacular scriptability makes it easy to do continuous integration and continuous delivery. It is also easy for non-developers to use.

There are three things that I especially like

- the revision graph view is excellent, and very nice to get an overview.

- p4merge visual layout

- The fact that there is no shadow folder, like in subversion or git

The way workspace view is setup. It is very often the biggest obstacle when introducing new users.

Also, it is very annoying that there is no easy way to download something from perforce, e.g. with a oneliner. If I have the p4 commandline installed,, and credentials, I think you should be able to download something, just to current directly, e.g. like git clone and them rm .git

The primary reason for our department for using Helix VCS compared to e.g. git is the innate support for big files.

The tool do it's job.

It's easy to customize it to adapt it to your need. Whether you want multiple depots, branches, workflow with intergrations, reviews or lock submit unless code is do build you can do that with little troubles.

It's scalability with clustering make it now an awesome tool that can be strong and efficient.

Beginners users will get lost in the tool chain by not understanding how p4 work exactly. The concept of file workspace knowledge based on the server side is hard to assimilate for them and leading to troubles

Admin could get lost in the knowledge base that is sometime too scattered.

All the pain of versioning files and ability to revert and jump back to a previous version. Ability to have several teams working on different feature in the same set of files without conflicts.

All what you can ask of a versioning solution but without the troubles of others

Perforce is the most fully-featured versioning system I've worked with. You can resolve pretty much any scenario you can think of. The shelving feature is extremely useful on occasion. It's very stable - never had it hang or crash.

It has a steep learning curve. Taking advantage of all the features requires putting some serious time and effort. It's a tool for the tech savvy. "Checking out" files is confusing when you're coming from SVN. Programmers on our team, as well as IT, are routinely asked for help with using even the visual client. Overall it's great for large projects where most people on the team have in-depth knowledge of how to use it. I would still use SVN for small projects where conflicts are less likely.

Perforce is great if you have a tech savvy team, working on fairly large projects. For small teams (<10 people) I would still recommend SVN or Git.

We're a games studio using Perforce for version control on all of our projects. Perforce is invaluable for programmers maintaining their sanity on larger projects.

Helix is a great alternative to other git services because any project you make is private and free. My team and I had gone through at least four other services and had left them either because of the limits in file size uploads, or we had simply hit the storage cap way too fast.

Perforce Helix in my opinion is the best solution short of renting your own server for indie game devs.

My only real complaint about helix is that their versioning client (P4V) tends to act up. When setting up my repo for the first time it decided to send it to System32 instead of the destination I had specified. P4V also seems to dislike stashing or discarding changes which can make it hard to consistently have new data from your project.

Helix is great, free, and powerful, but be aware of possible bugs like the ones I had mentioned in my review and make sure to read through the tutorials and documentation to make sure that everything goes off without a hitch.

Perforce solved our source control problem quite will after fiddling with it and getting used to its quirks, all in all it is a great service and can only get better from here.

Perforce can handle heavy artifacts like it is cakewalk and the security settings along with permission system is really comprehensive, best suited for large organizations which need good security.

The distributed features are not inherent to the VCS and traditionally it is a Client-Server VCS remodeled to copy features from git. I feel there should be more self-innovated features rather than just copying git.

I am helping our client secure their source code by providing a secure alternative for storing source code and artifacts in a safe place.

P4V made life easy with visual version control.

Added Swarm review improved our code quality.

Some times it asks for P4V password while doing some operations. But there is no way to authenticate password. Only way is to change password.

Swarm is good, for big teams there are high chances same file modified by other people same time.

After Swarm review approved and if we merge others changes it asks for review again. This blocks our check-in for review again delays our development time.

It is easy to learn and use.

Amazing features needed for developers and organizations with big number of people.

Version control for many models by branching same code. Merge restrictions for Integration branches etc.

The software is easy to manage from an administrative standpoint. We installed and it just keeps going. I support a wide variety of apps, and this is by far the easiest to upgrade/patch. For the few times we have had to do any sort of recovery, it was also quick and painless. This product is a software administrator's dream.

I wish that the platform had some sort of reporting capability. The biggest request I get from the community is asking for metrics on the repository that I can't give without some creative scripting.

When we added Helix Swarm to our existing P4 installation we were finally able to do code review between different geographical sites efficiently. Swarm has helped standardize our code review process, and given us the ability to track our reviews more easily.

Generally, I like that Helix operates well at large scales; I have to support almost 1000 users, and the performance problems are much smaller than they could be.

I have major issues with the integration functionality, two specific problems in particular. For one thing, the fact that Helix is smart enough to recognize when files have been moved, but by default chooses not to use that power in integration, seems fatally flawed. Second, it is bizarre to me that the only way to undo an integration is to delete metadata; Helix provides both "rollback" and "backout" capabilities, but none of those touch the integration history, which inevitably leads to the situation where a developer wants to back out changes and then re-integrate from trunk, but is forced to perform an elaborate hopscotch routine of integrations, backouts, and re-backouts to do so. This is absurd

At the moment, Helix supports 90% of our version control needs.

Perforce is a solid VCS. Its centralized nature makes it faster and more scalable than git or mercurial, but its merge tracking is far better than Subversion's. It's very reliable too. It also comes with a decent built-in code review tool, Swarm.

p4d is proprietary software, with all the attendant problems. It's needlessly difficult to install, because Perforce doesn't understand how the OSS community distributes software. Worst of all, after many years Perforce dropped support for our operating system, FreeBSD. They even accept payment for our license renewal without telling us that they were abandoning it. Now we're in a bind. We can't easily migrate away from Perforce because it stores merge tracking information in a way that is incompatible with other VCS tools. Worst of all, we have good reason to believe that newer versions of p4d aren't using any APIs unavailable on FreeBSD. So if we had source access, we could simply recompile it. But that sadly isn't an option with proprietary software.

Don't. Use an open-source VCS instead, or you may get trapped.

It's our primary VCS. It does everything that any VCS would do.

Perforce Helix is much more than the version control you are used to, be it Git, SVN or even Dropbox. It brings much more features than you expect: history, branching, reviews, locks. Everything in a unified platform.

Don't expect to use it like Dropbox, it's not as easy as dropping files on a directory. The same goes for developers used to other VCS. Coming from git was not smooth.

All the features bring complexity for the tool.

Perforce Helix should be taken in consideration if you team is big enough and the usual VCS tools already look too simple for you use case.

We are a creative studio focused on game development, website creation and animation. With our team growing on the past project we found it really hard to manage the assets generate by the art team. Perforce appeared as a VCS solution, suited for the creative world.

Perforce is fast and I know exactly which repository to start looking at... there is only one and we have it replicated to multiple sites providing rapid access to users all over the world with lower bandwidth requirements.

Perforce support is amazing. They really take the time to help with workflows, understanding how to build a more efficient pipeline and many other things.

The Auditing capabilities allows us to see how people are using the product and helps us find trends.

Perforce upgrades could be more automatic, but I like the security of knowing what versions are running. We

With Perforce we are able to keep everything where it can be found easily. With Git we have to sew back together our codebase it is so easy in perforce to branch and to merge branches, sewing together git repositories is a huge challenge.

Having the repository centrally controlled, without having a .svn or .git folder on your drive is a huge boon. Another feature is the ability to mark files as "one copy on server" only so that binaries can be kept in sync quickly.

The integration with game engines like Unity leave a bit to be desired. there doesn't appear to be support for the "p4config" file which we rely on for maintaining multiple servers.

the free version is a bit limited, and they insist on buying a support contract when buying the software. We NEVER once called their support line, so it's just a money grab

We do game development with a virtual team, source code control is crucial

It's fast and easy to track the changes my team is making to our repo. I can quickly look at the history of an asset and manage a large number of branches with relative ease. Simple enough for almost anyone to use, but very powerful suite of options for customizing it to your team's needs.

Some admin functions still require command prompts that require sifting through documentation and lots of trial and error to figure out. I wish it were easier to lock/unlock checked-out files with admin privileges.

Version control is imperative for any medium-large team working in a fast-paced development environment.

I enjoy the fact that minimal adoption is simple, still using git and the tooling around the base code repository management that most developers are used to. All the other tooling on top is amazing, when used properly. The integrations with the design tool and the office tools looked like they did the job well, although I never had direct hands on with them.

Without a proper adoption or internal champion, the software gets mistreated and used only for git repo usage. This isn't a fault of the software per-se, but the adoption process of the software. I would love to see more integrations with 3D modeling and audio tooling, as I work in video games. Additionally, the GUI visual merge tools could do with a little more polish - but I generally use the command-line for my interactions.

Helix is a great toolset, but make sure you processes are in a point to support all it offers. If you implement a software like this in hopes of building processes, you won't get the full benefits or get proper adoption. Trying to give tools to a designer without proper understanding of the end-goal of versioning is not the best way to adopt such a wonderful tool.

We are mainly trying to have internal git hosting, but I am sure upper management wanted to keep tabs on our interactions. Some staff had been known to take files from projects and use them in their personal work. I am sure that helped shed light on those aspects with some of the detection tooling. We were also trying to get designers and non-poweruser-developers into the entire project versioning mentality.

Being able to shelve changes and unshelve them on other branches and other machines is fantastic.

The UI can be a little slow. The fuel gauge in the bottom right of the window seems to bear no relation to reality.

We have a huge code and data solution which Helix easily swallows and versions for us quite happily.

I like the File Explorer and Photoshop plugins for Windows. This allows me to very quickly check in and check out files without having to find them in the p4v client.

Branching is lacking. Unlike Git, branching is very linear. This makes it difficult to identify the ancestry of a commit.

Here at work, we are using Helix Perforce as the version control system for our local web and software development.

I can have one massive repository (depot) or lots of small ones. I can control exactly which parts of any depots I want to download, I don't have to sync an entire depot.

Some of the IDE plugins (third party) can be immature and sometimes buggy.

Software development.

Our repository is very large due to the various binaries we store. This eliminates many of our other options out there. Our studio of veteran game developers have been working with P4 throughout their professional careers. After a brief stint with SVN and Git, it was nice to come back home to P4.

I wish P4 had its own depot hosting service that could accomodate out very large repository

Amazon AWS EC2 with elastic block storage

Depot for code, art assets, and binaries

It does the job without the clutter and overhead of more complex alternatives. It is easy to use and performs a lot faster and reliable than the previous two source control products.

Streams needs to be updated to be able to manage multiple releases better.

It help me maintain multiple common code lines and provide a visual development workflow using streams.

1. How intuitive and user friendly the software is.

2. The user guide is very helpful

3. Easy to use UI.

4. Speed of getting results

1. There are some bugs which need fixing.

2. Constant refreshing is needed.

3. The results are not always updated soon enough.

4. Sometimes there is a mismatch between what is there in the server and what is shown at client side

1. Source control

2. Automated build.

3. Automated testing

It has its own user interface, I don't have to depend on third party programs to use them as User interfaces. We are using perforce for source control management storing code, documents and binaries

I still haven't figure out the best way to create a branch of a older version. I always run into issues.

For college, I can have repositories and depots to work on my projects safely creating branches and directories.

Reliable, have used for the past two decades and have never had any data loss.

Command line based (there is a GUI as well but not nearly as good). Powerful and easy to learn.

Helix4Git. Causes lots of internal pressure as some developers like git and others perforce, so this is used as a wedge for git users rather than having a consistent environment.

Git is free. The yearly cost for perforce is not small, and while support is awesome, if you are a good admin, git is not a major burden.

Source code management

Protecting source code from data loss

tracking where source code goes (primarily for security purposes)

Native support for DVCS is my favorite feature with streams being an equal. I cannot state enough how important it is having a stable version control system that does not lose your history and shows you what streams have to be updated by changes made by other users.

My biggest grip is with p4v for macOS, in which you can connect to a DVCS, but the connection only works once and after that, there are failures reported by the app that does not seem to be addressed by Perforce.

Understand that p4helix supports not just p4 but other systems like git and svn.

Development of iOS and macOS apps.

What I like best about Helix is the centralized features, full support of Git, and user-friendly and intuitive UI. It's easy for non-technical users to understand which is critical to small and large teams alike.

The P4V versioning client seems to have problems from time to time which can cause delays in production. 3rd party tools integration support would be nice to see.

I would recommend that you give the free trial a chance.

Source code control with an international team can be a difficult task to handle. Perforce helped with this issue and made it easy for all our staff, including non-technical employees, to understand versioning.

It is best suited for small project, big projects - projects of any size.

Granularity of access control is great.

Great tool for today’s CI/CD solutions.

Excellent support

It demands for bigger HW resources compared to GIT

It demands for larger admin team compared to GIT

Not dynamic as GIT

Must checkout tool for your SCM solutions

Build a single source of truth for all our IP

The best part of this software is how elegantly it handles merges and easy it is to use. Shelves are awesome to allow others to look at your work and everything else just makes sense.

The interface is not the most attractive, but it works. It can be confusing to understand how workspaces and streams work.

I definitely recommend that you use this for version control if it works with your develop environment. It is way better than SVN or Git and causes way less problems in the long run.

This software helps us version control our code and helps us make games efficiently.

Setting up a depot in Helix Cloud is simple and only takes a few minutes. The web interface gives non-technical team members access to the depot without having to deal with the normal perforce client.

Helix Cloud's web interface is great for basic operations but there is still a lot that you have to do through a client. I would like to see it's functionality expanded.

Being able to add a team member through Helix Cloud's web interface and they can start downloading and uploading files without having to walk them through how source control software works is hugely beneficial.

Helix Swarm allows me the power to review my team's code, automate QA verification status, and limiting commits to approved & verified code.

Swarm allows a lot of automation, but it would really be useful if the Perforce 'changes -i' command worked with shelved changes (as opposed to committed changes), to more easily identify change origins from integrations.

Helix allows us to maintain versions of code going back over 10 years, and gives us the ability to rebuild any historical version. Helix also gives us the ability to work on both private and group branches, to more easily segment our workflow.

Ease of use, ease to admin. The capability of Helix to handle such a huge code base of the company with so much of features to offer.

Swarm allows a lot of automation with shelved changes (as opposed to committed changes), to more easily identify change origins from integrations.

Software QA

The capability of Helix to handle such a huge code base of the company with so much of features to offer.

The Helix behavior with in house written perforce trigger should be supported.

We deliver lot of products on daily basis and development team will create lot of branches which helps them in fixing & testing the bug very fast.

Pretty good SCM overall. Perforce has very good tech support.

Perforce have some well known limitations that have to do with the origins of the product.

For instance it has no ability to create empty folders. User cannot work offline like in Git for example.

Also a couple things in the client software could be improved.

Overall, it works well.

Centralizing the source code for the division.

Perforce comes with a user-friendly and feature-rich GUI client. Keeping the learning curve low is very important for big production teams, which usually consist of people with different technical background.

Version control systems should not make use of the read-only flag on files to keep track of open-for-edits. The server only runs on Windows, and there is no straightforward way to backup the depots.

Version control for source code and digital assets. Perforce is a good option if you need good binary file support out of the box.

Perforce and Helix are great solutions for version control. Compared to Git, there is much better control over binary assets, which is extremely important for certain projects. Perforce is heavily used at other companies working on similar products, and many users are more comfortable with these products.

Not open source and requires a little more legwork to get set up. Is overkill for small, single person projects or strictly code-based projects.

Group collaboration and keeping everyone in sync and working on the same version of the product.

Perforce is a scalable system that works well in a large organization with a lot of users and different permission requirements. Integration with third-party systems like Jenkins and Jira is good.

I like the Swarm review system and possible integration with Jenkins for blocking commits based on test builds.

Without proper replica servers, a centralized perforce server can be slow.

Perforce works well in an enterprise environment especially with a lot of large files.

Efficient exchange and tracking of IP in a large organization.

Faster development on multi site projects.