Perforce Helix Core
Perforce | 1.0.0Linux/Unix, Other openlogic/rockylinux-9-hardened - 64-bit Amazon Machine Image (AMI)
Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Perforce for everything
What do you like best about the product?
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
Granularity of access control is great.
Great tool for today’s CI/CD solutions.
Excellent support
What do you dislike about the product?
It demands for bigger HW resources compared to GIT
It demands for larger admin team compared to GIT
Not dynamic as GIT
It demands for larger admin team compared to GIT
Not dynamic as GIT
What problems is the product solving and how is that benefiting you?
Build a single source of truth for all our IP
Recommendations to others considering the product:
Must checkout tool for your SCM solutions
- Leave a Comment |
- Mark review as helpful
Best versioning tool i have used so far
What do you like best about the product?
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.
What do you dislike about the product?
not having the facility of creating personal branches and tracking versions for them
What problems is the product solving and how is that benefiting you?
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
Recommendations to others considering the product:
its a good tool if u r considering client server versioning model
Perforce SCM
What do you like best about the product?
Pretty good SCM overall. Perforce has very good tech support.
What do you dislike about the product?
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.
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.
What problems is the product solving and how is that benefiting you?
Centralizing the source code for the division.
Solid versionning software that is scalable
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
Admin could get lost in the knowledge base that is sometime too scattered.
What problems is the product solving and how is that benefiting you?
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
All what you can ask of a versioning solution but without the troubles of others
Not Overly Complex
What do you like best about the product?
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.
What do you dislike about the product?
Streams needs to be updated to be able to manage multiple releases better.
What problems is the product solving and how is that benefiting you?
It help me maintain multiple common code lines and provide a visual development workflow using streams.
Perforce Helix - version control for all.
What do you like best about the product?
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.
What do you dislike about the product?
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.
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.
What problems is the product solving and how is that benefiting you?
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.
Easy Scaleable and helpfull
What do you like best about the product?
Scalability and easy administration.
Amazing serverside data compression.
Great support
Amazing serverside data compression.
Great support
What do you dislike about the product?
There could be even more integrations to other systems.
What problems is the product solving and how is that benefiting you?
Version management system
Solid core server product
What do you like best about the product?
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.
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.
What do you dislike about the 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.
What problems is the product solving and how is that benefiting you?
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.
A powerful, scalable source control and security tool
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
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.
Recommendations to others considering the product:
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.
Decent version control system
What do you like best about the product?
Easy to use Perforce/Helix UI client for basic usercase
What do you dislike about the product?
Harder to use the functions as you use it more....
What problems is the product solving and how is that benefiting you?
Version control for configuration
Recommendations to others considering the product:
Make the complex functionality like check in and other other features easy to use or learn.
showing 71 - 80