Git vs. Octopus Deploy

GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.

Incentivized

Octopus Deploy is well suited for our requirements of deploying across multiple environments with one consistent release. We are saving a lot of time by not having to package and move release files around. Our release process is more efficient and consistent with automation. There are some parts that we could probably perform with existing tools such as DevOps and there are one or two features we have to workaround to fit for our setup such as the step templates to install websites. These are minor in our opinion.

Incentivized

• Ability to create branches off current releases to modify code that can be tested in a separate environment.
• Each developer had their own local copy of branches so it minimizes mistakes being made.
• Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
• Conflicts are displayed nicely so that developers can resolve with ease.

Incentivized

• Octopus integrates nicely with TeamCity, our build server.
• Octopus uses the same deployment packages across environments and makes it easy to track their progress across those environments.
• Octopus makes it easy to handle configuration across environments which is usually a particularly difficult task.

Incentivized

• There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
• Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
• Many different GUIs, many people (including myself) opt to just use the command-line.

Incentivized

• In the past has been somewhat .net focused but that has been changing in recent times
• Would be great if community licenses for NFP organizations were perpetual - but in saying that I appreciate that Octopus does provide my organization with a community [license]. Not all organisations do
• I can’t think of any other

Incentivized

Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.

Incentivized

Would be a 10 except for the retirement of the free Community Edition.

Incentivized

Git is easy to use most of the time. You mostly use a few commands like commiting, fetch/pull, and push which will get you by for most of time.

Incentivized

Octopus Deploy has greatly helped us to improve our reliability and frequency of our deployments and given us the confidence to deploy much more often, with a direct benefit to customers. Cross-platform support and release to Cloud require more focus on the product side.

Incentivized

Octopus Deploy is a software that runs very effectively, is easy to use, does not require such a high learning curve, provides the necessary tools to carry out the functions it offers, making it a very flexible software, it also allows that can be configured according to the needs of the user and provides integrations with other very advantageous tools since they are carried out in a very favorable way.

Incentivized

I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.

Incentivized

Octopus Deploy support has always been there for us, even when using the free tier, we get responsive hands-on help. We haven't needed to use that level of support since the documentation is clearly written, and help is readily available within the interface itself. Using Octopus Deploy is a truly joyful experience.

Incentivized

It's easy to set up and get going.

Incentivized

I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different.
The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy.
It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.

Incentivized

There aren't really any competitors in the land of ASP.NET. Deployment is too ad-hoc. Other tools exist that have massive downsides, like Web Deploy. Most aren't even supported anymore. You could argue that containers (Docker) are a competitor, but containers cannot be used for everything and solve a somewhat different problem. Octopus Deploy is even able to help with containers. To us, Octopus Deploy was really the only really polished solution.

Incentivized

Great support from professional services.

Incentivized

• Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
• Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
• Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.

Incentivized

• Allows us to deploy to our fleet quickly and without interruption to service
• Can roll back to previous releases quickly, allowing us to back out of breaking changes in the worst-case scenarios.
• Integration with several targets has allowed us to explore new platforms for our products, such as Docker in AWS ECS.

Incentivized