Perforce P4 (formerly Helix Core) is the company's version control and peer code review solution. Perforce offers add-on products for code review for free, and Git support products.
N/A
Sourcetree
Score 7.1 out of 10
N/A
Sourcetree, by Atlassian, is a free version control client for Mac and Windows that works with Git and Mercurial repositories. It's distributed version control allows developers to visualize code, review changesets, stash, cherry-pick between branches or commit with a single click.
In my opinion, Perforce Helix Core is on a top level of irritation and anti-user experience. In my experience, I can't do simple things like 1 word file edits, while I have never been confused when using something based on Git.
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.
New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that …
My last two jobs used SmartSVN but it required a paid license to use regardless of the number of users. The initial setup for Perforce was much more difficult than SmartSVN. There is a lot of parity between the two software packages even though the terminology can be different. …
Perforce has a better built native visual client that is much simpler to use than Git's. It has a lot of optimizations in the workflow that can execute common patterns during a usual workday. Perforce also has an easier to understand method of presenting merge conflicts and …
Perforce is internally hosted, which makes it quite a bit faster. I found it easier to use that GitHub and Bitbucket, at least in terms of checking out files and creating changelists. GitHub and Bitbucket are much better for smaller teams, as they are cloud hosted, making …
Today's web based software makes them easier to integrate into a development process. Jira with integrated BitBucket as the versioning tool, is ahead of the competition. However for large organizations, Perforce is still a very good choice. GitHub can be used as free tool, but …
Perforce has more features than SVN. However even the simpler tasks in SVN require a degree more technical aptitude with Perforce. Git offers most of the same features, however most of these are only really supported via the command-line in Git, where as most tasks can be …
Perforce is similar to SVN but the SVN has better command line support. Git surpasses both SVN and Perforce because of its flexibility with multiple branches and code review.
I actually recommend Github Desktop for any developer who uses git. It's far more friendly, has good functionality but not overwhelming, and you don't need to use it for github repos. Sourcetree is only good for if you're wanting to perform complex actions or audit historical …
Sourcetree allows seamless integration across all widely used GIT services and is cross-platform compatible. This client is capable of managing workflows of any difficulty and its cross-compatibility eliminates the need to use different or multiple GIT clients altogether.
I tried GitHub Desktop for a couple of days, but it is just not visual enough for me. It has no graph display for branches. Too much clicking is required to get info that the Sourcetree UI shows by default. Sourcetree gives you that "Big Picture" dashboard. GitHub Desktop seems …
Free to use, integrated with useful features like Mercurial, Git LFS, submodules etc, helps new user to learn best practices. With all these features along with tools implemented for authentication and securing repos it becomes the best candidate in front of the competition. If …
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.
We have a need to consolidate into a single package, and have such a large variety of technical proficiency among our users that Perforce seems less suitable. Many would like to remain using it, however, even those who use Perforce are the minority, and are often limited to our development teams.
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!
We help new users onboard quickly and then use Sourcetree to handle their day-to-day SCM needs for managing CIs (Configuration Items). We can visually show management the branching and commit history to show the flow and pace of development.
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.
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.
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.
New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that requires hours to pull together that would take me less than 30 seconds in Perforce Helix. Large file storage in Bitbucket is clunky and requires you to jump through too many hoops. It's not even something you have to think about with Perforce Helix, as you are only limited by your OS. Perforce Helix is very easy to use even for non-developers. I wouldn't dare ask a non-developer to store their documentation in Bitbucket.
I tried GitHub Desktop for a couple of days, but it is just not visual enough for me. It has no graph display for branches. Too much clicking is required to get info that the Sourcetree UI shows by default. Sourcetree gives you that "Big Picture" dashboard. GitHub Desktop seems unfinished to me due to its lack of this overview screen.
In my experience, using Sourcetree actually slows down development if you're the average developer needing to do simple git actions. Getting set up is fast, but the learning curve to use the tool is just too steep if you're just looking to push, pull, commit, branch etc.
Sourcetree is not implemented by default at our company, but is recommended as we primarily use Atlassian products. However the lack of integration with other Atlassian products means that this git GUI doesn't give any more or less ROI for your Atlassian ecosystem compared to another git GUI tool.
For auditing and exploring history Sourcetree can be very helpful. Having all of this information in one place with a plethora of actions and tools at your disposal means you can audit repos much quicker than any other git GUI or online repo explorer.
