GitKraken vs. PeopleOne vs. Perforce P4

The software is easy to use and share within our team. Licensing and setup is straightforward. The product just works and we love it.

Incentivized

We are using [PeopleONE] to collect and manage our field data for payroll, invoicing, and production management purposes. So far, it works quite well for those uses. Additionally, we are using the app to manage communications from our offices to our field management at upper and middle field management levels. We have successfully used the application to communicate important upcoming events, COVID protocols and reporting processes, and other initiatives. I am unfamiliar with the limitations of this technology or applications for which it would be unsuited.

While Perforce Helix is the best version control software out there, it can also be used to track your documentation, training videos and materials, and requirements. If you have strict compliance requirements, it can be used to ensure that those requirements are satisfied. Perforce Helix is incredibly flexible and can meet the needs of individual users as well as companies with thousands of users.

Incentivized

• Customizable workflow steps help organize projects
• Time tracking down to seconds helps to estimate sprints
• Burndown charts let you know when to plan your next release

Incentivized

• The UI, both for desktop and mobile apps, is simple and virtually self-explanatory.
• Compared to apps we have used in the past, PeopleONE is fast, in both data entry and retrieval.
• The team responsible for creating our specific requirements for the app is exceptionally responsive. It is made up of creative problems solvers who have built a product that meets every need we have presented.

• 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.

Incentivized

• Timing Out - when editing a story or bug, occasionally Axosoft will time out and all changes will be lost
• Viewing past sprints can be hard to locate
• Multiple users within a Story - Axosoft could do a better job managing multiple users on the same story
• User Interface isn't entirely user friendly and looks a bit outdated

Incentivized

• We haven't actually experienced any issues of note to record here. Every concern, requirement, or change we have requested has been swiftly and satisfactorily resolved by the Impiger team.

• Perforce tends to feel backwards in how it approaches certain tasks, like branching and integrating - even once you figure out how it wants you to perform these tasks, you will likely forget when it comes around to the next time you need to do them again.
• Perforce has a higher price tag, comparatively.
• Perforce make some tasks very easy, and yet other tasks very difficult - it doesn't always seem to have found its target user's proficiency.

Incentivized

[I give it this rating] because it has addressed all of our needs in a succinct manner and it operates efficiently.

We are fully committed to our use of Perforce. It works well within our organization and our desire to share our code base with our customers. Their support staff are responsive, inquisitive, and eager to improve their software. I feel like we have a direct line to their design/feature team as they often solicit our feedback.

Incentivized

Over the years, I have used many Git tools, but GitKraken stands out. It's now my favorite Git tool by far—excellent graphical overview of the branches, straightforward usage of all functionality, and lots of integration available. Currently, I am using GitKraken to connect to the ADO and quickly create PRs, using gitflow and tracking the work of my team mates.

Incentivized

With Perforce Helix, you can use it via the command line, via P4V, or any of the other APIs included with the product. It is extremely easy for new users to get up and running. Users of Perforce Helix only have to pull in the files of interest to them. Also, Perforce is very easy to script and integrate into your CI/CD pipeline. Streams allows you to have pinpoint control of your workflow, and P4Search is the absolute best--I wish Perforce (the company) would talk more about this. It is absolutely fabulous!

Incentivized

In our large environment, Perforce is rarely "down". We have regular maintenance windows and from time to time Perforce can feel a little slow, but its always available. Tech support has always worked with our engineers and IT department to make sure that any real performance or stability issues are addressed quickly.

Incentivized

I had two representatives from Perforce contact me after downloading it but never responded when I had questions. I also had a difficult time finding good training material for getting started. There is a lot of available support material when running into issues, though, because of how many large companies use it.

Incentivized

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.

Incentivized

I actually like JIRA better, to me the UI is a lot cleaner. Easier to use, and search tickets.

Incentivized

Git is great, I love Git. But it's not great for dealing with binary assets, even when using Git LFS. Locking is not as simple as on perforce. Git presents some problems on using for non-tech people it can get overwhelming and tech people have to come by and help.

Incentivized

• Productivity bump for developers over previous software
• Code is never gone forever and can be found if needed
• Allows us to collaborate and finish projects faster

Incentivized

• Improved accuracy of data collected
• Improved efficiency of data collected
• Improved efficiency of payroll and invoicing processes
• Decreased time, in the field and in the office, involved in managing data

• Decreased our implementation costs by allowing versioning and back out of customizations made in the field.
• saves developers time through automation of changes between branches - they think less of the plumbing and have more time to write code.
• Downside is training/managing expectations of new developers who come in assuming they will use Git.

Incentivized