Alternatives to GitHub logo

Alternatives to GitHub

GitLab, Bitbucket, AWS CodeCommit, Git, and SVN (Subversion) are the most popular alternatives and competitors to GitHub.
286K
249.8K
+ 1
10.3K

What is GitHub and what are its top alternatives?

GitHub is a popular web-based platform for version control and collaboration using Git. It allows users to host and review code, manage projects, and build software alongside other developers. GitHub offers features such as code hosting, pull requests, issue tracking, and project management tools. However, GitHub does have limitations such as restrictions on private repositories for free users and dependency on a stable internet connection for collaboration.

  1. GitLab: GitLab is a more complete DevOps platform than GitHub, offering features like CI/CD pipelines, container registry, and integration with Kubernetes for container orchestration. Pros include a more robust CI/CD system and integrated DevOps tools, while cons include a steeper learning curve compared to GitHub.
  2. Bitbucket: Bitbucket offers both Git and Mercurial repositories and integrates seamlessly with Jira for issue tracking. Key features include built-in CI/CD pipelines and integration with other Atlassian products. Pros include better integration with Atlassian tools and support for private repositories, while cons include a smaller user base compared to GitHub.
  3. GitKraken: GitKraken is a Git client with a visually appealing interface that simplifies complex Git commands. It offers features like GitHub integration, drag-and-drop functionality, and a built-in code editor. Pros include an intuitive user interface and seamless GitHub integration, while cons include limited collaboration features compared to GitHub.
  4. SourceForge: SourceForge is an open-source software development platform that offers free hosting for open-source projects. Key features include version control, project management tools, and a marketplace for developers to showcase their projects. Pros include free hosting for open-source projects and a large community of developers, while cons include a less modern interface compared to GitHub.
  5. Gitea: Gitea is a lightweight self-hosted Git service that offers features like repository management, issue tracking, and pull requests. Pros include easy deployment and low resource consumption, while cons include limited scalability compared to GitHub.
  6. Beanstalk: Beanstalk is a version control platform that offers Git and Subversion repositories along with deployment tools. Key features include code review, continuous integration, and deployment automation. Pros include a simple setup process and intuitive interface, while cons include limited support for third-party integrations compared to GitHub.
  7. Phabricator: Phabricator is an open-source software development platform with features like code review, repository hosting, and task management. Pros include comprehensive project management tools and support for code reviews, while cons include a complex setup process compared to GitHub.
  8. Perforce: Perforce Helix Core is a version control system designed for enterprise-scale development with features like distributed architecture, support for large files, and high performance. Pros include scalability and performance for large projects, while cons include a higher cost compared to GitHub.
  9. AWS CodeCommit: AWS CodeCommit is a fully managed source control service that hosts secure private Git repositories with features like access control, encryption, and AWS integration. Pros include seamless integration with other AWS services and secure repository hosting, while cons include a lack of social coding features compared to GitHub.
  10. SourceHut: SourceHut is an open-source platform that offers version control and project hosting with a focus on simplicity and privacy. Key features include Git hosting, mailing lists, and issue tracking. Pros include a privacy-focused approach and support for multiple VCS, while cons include a less polished user interface compared to GitHub.

Top Alternatives to GitHub

  • GitLab
    GitLab

    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers. ...

  • Bitbucket
    Bitbucket

    Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users. ...

  • AWS CodeCommit
    AWS CodeCommit

    CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

  • SVN (Subversion)
    SVN (Subversion)

    Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ...

  • Azure DevOps
    Azure DevOps

    Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support. ...

  • Jira
    Jira

    Jira's secret sauce is the way it simplifies the complexities of software development into manageable units of work. Jira comes out-of-the-box with everything agile teams need to ship value to customers faster. ...

  • Git Flow
    Git Flow

    It provides excellent command line help and output. It is a merge based solution. It doesn't rebase feature branches. ...

GitHub alternatives & related posts

GitLab logo

GitLab

61.9K
2.5K
Open source self-hosted Git management software
61.9K
2.5K
PROS OF GITLAB
  • 508
    Self hosted
  • 431
    Free
  • 339
    Has community edition
  • 242
    Easy setup
  • 240
    Familiar interface
  • 137
    Includes many features, including ci
  • 113
    Nice UI
  • 84
    Good integration with gitlabci
  • 57
    Simple setup
  • 35
    Has an official mobile app
  • 34
    Free private repository
  • 31
    Continuous Integration
  • 23
    Open source, great ui (like github)
  • 18
    Slack Integration
  • 15
    Full CI flow
  • 11
    Free and unlimited private git repos
  • 10
    All in one (Git, CI, Agile..)
  • 10
    User, group, and project access management is simple
  • 8
    Intuitive UI
  • 8
    Built-in CI
  • 6
    Full DevOps suite with Git
  • 6
    Both public and private Repositories
  • 5
    Integrated Docker Registry
  • 5
    So easy to use
  • 5
    CI
  • 5
    Build/pipeline definition alongside code
  • 5
    It's powerful source code management tool
  • 4
    Dockerized
  • 4
    It's fully integrated
  • 4
    On-premises
  • 4
    Security and Stable
  • 4
    Unlimited free repos & collaborators
  • 4
    Not Microsoft Owned
  • 4
    Excellent
  • 4
    Issue system
  • 4
    Mattermost Chat client
  • 3
    Great for team collaboration
  • 3
    Free private repos
  • 3
    Because is the best remote host for git repositories
  • 3
    Built-in Docker Registry
  • 3
    Opensource
  • 3
    Low maintenance cost due omnibus-deployment
  • 3
    I like the its runners and executors feature
  • 2
    Beautiful
  • 2
    Groups of groups
  • 2
    Multilingual interface
  • 2
    Powerful software planning and maintaining tools
  • 2
    Review Apps feature
  • 2
    Kubernetes integration with GitLab CI
  • 2
    One-click install through DigitalOcean
  • 2
    Powerful Continuous Integration System
  • 2
    It includes everything I need, all packaged with docker
  • 2
    The dashboard with deployed environments
  • 2
    HipChat intergration
  • 2
    Many private repo
  • 2
    Kubernetes Integration
  • 2
    Published IP list for whitelisting (gl-infra#434)
  • 2
    Wounderful
  • 2
    Native CI
  • 1
    Supports Radius/Ldap & Browser Code Edits
CONS OF GITLAB
  • 28
    Slow ui performance
  • 9
    Introduce breaking bugs every release
  • 6
    Insecure (no published IP list for whitelisting)
  • 2
    Built-in Docker Registry
  • 1
    Review Apps feature

related GitLab posts

Tim Abbott
Shared insights
on
GitHubGitHubGitLabGitLab
at

I have mixed feelings on GitHub as a product and our use of it for the Zulip open source project. On the one hand, I do feel that being on GitHub helps people discover Zulip, because we have enough stars (etc.) that we rank highly among projects on the platform. and there is a definite benefit for lowering barriers to contribution (which is important to us) that GitHub has such a dominant position in terms of what everyone has accounts with.

But even ignoring how one might feel about their new corporate owner (MicroSoft), in a lot of ways GitHub is a bad product for open source projects. Years after the "Dear GitHub" letter, there are still basic gaps in its issue tracker:

  • You can't give someone permission to label/categorize issues without full write access to a project (including ability to merge things to master, post releases, etc.).
  • You can't let anyone with a GitHub account self-assign issues to themselves.
  • Many more similar issues.

It's embarrassing, because I've talked to GitHub product managers at various open source events about these things for 3 years, and they always agree the thing is important, but then nothing ever improves in the Issues product. Maybe the new management at MicroSoft will fix their product management situation, but if not, I imagine we'll eventually do the migration to GitLab.

We have a custom bot project, http://github.com/zulip/zulipbot, to deal with some of these issues where possible, and every other large project we talk to does the same thing, more or less.

See more
Joshua Dean Küpper
CEO at Scrayos UG (haftungsbeschränkt) · | 20 upvotes · 743.6K views

We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

See more
Bitbucket logo

Bitbucket

40.5K
2.8K
One place to plan projects, collaborate on code, test and deploy, all with free private repositories
40.5K
2.8K
PROS OF BITBUCKET
  • 905
    Free private repos
  • 397
    Simple setup
  • 349
    Nice ui and tools
  • 342
    Unlimited private repositories
  • 240
    Affordable git hosting
  • 123
    Integrates with many apis and services
  • 119
    Reliable uptime
  • 87
    Nice gui
  • 85
    Pull requests and code reviews
  • 58
    Very customisable
  • 16
    Mercurial repositories
  • 14
    SourceTree integration
  • 12
    JIRA integration
  • 10
    Track every commit to an issue in JIRA
  • 8
    Deployment hooks
  • 8
    Best free alternative to Github
  • 7
    Automatically share repositories with all your teammates
  • 7
    Source Code Insight
  • 7
    Compatible with Mac and Windows
  • 6
    Price
  • 5
    Login with Google
  • 5
    Create a wiki
  • 5
    Approve pull request button
  • 4
    Customizable pipelines
  • 4
    #2 Atlassian Product after JIRA
  • 3
    Unlimited Private Repos at no cost
  • 3
    Also supports Mercurial
  • 3
    Continuous Integration and Delivery
  • 2
    Mercurial Support
  • 2
    Multilingual interface
  • 2
    Teamcity
  • 2
    Open source friendly
  • 2
    Issues tracker
  • 2
    IAM
  • 2
    Academic license program
  • 2
    IAM integration
CONS OF BITBUCKET
  • 19
    Not much community activity
  • 17
    Difficult to review prs because of confusing ui
  • 15
    Quite buggy
  • 10
    Managed by enterprise Java company
  • 8
    CI tool is not free of charge
  • 7
    Complexity with rights management
  • 6
    Only 5 collaborators for private repos
  • 4
    Slow performance
  • 2
    No AWS Codepipelines integration
  • 1
    No more Mercurial repositories
  • 1
    No server side git-hook support

related Bitbucket posts

Michael Kelly
Senior Software Engineer at StackShare · | 14 upvotes · 956.7K views

I use GitLab when building side-projects and MVPs. The interface and interactions are close enough to those of GitHub to prevent cognitive switching costs between professional and personal projects hosted on different services.

GitLab also provides a suite of tools including issue/project management, CI/CD with GitLab CI, and validation/landing pages with GitLab Pages. With everything in one place, on an #OpenSourceCloud GitLab makes it easy for me to manage much larger projects on my own, than would be possible with other solutions or tools.

It's petty I know, but I can also read the GitLab code diffs far more easily than diffs on GitHub or Bitbucket...they just look better in my opinion.

See more
Shared insights
on
GitHubGitHubGitLabGitLabBitbucketBitbucket

A bit difference in GitHub and GitLab though both are Version Control repository management services which provides key component in the software development workflow. A decision of choosing GitHub over GitLab is major leap extension from code management, to deployment and monitoring alongside looking beyond the code base hosting provided best fitted tools for developer communities.

  • Authentication stages - With GitLab you can set and modify people’s permissions according to their role. In GitHub, you can decide if someone gets a read or write access to a repository.
  • Built-In Continuous Integrations - GitLab offers its very own CI for free. No need to use an external CI service. And if you are already used to an external CI, you can obviously integrate with Jenkins, etc whereas GitHub offers various 3rd party integrations – such as Travis CI, CircleCI or Codeship – for running and testing your code. However, there’s no built-in CI solution at the moment.
  • Import/Export Resources - GitLab offers detailed documentation on how to import your data from other vendors – such as GitHub, Bitbucket to GitLab. GitHub, on the other hand, does not offer such detailed documentation for the most common git repositories. However, GitHub offers to use GitHub Importer if you have your source code in Subversion, Mercurial, TFS and others.

Also when it comes to exporting data, GitLab seems to do a pretty solid job, offering you the ability to export your projects including the following data:

  • Wiki and project repositories
  • Project uploads
  • The configuration including webhooks and services
  • Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities.

GitHub, on the other hand, seems to be more restrictive when it comes to export features of existing GitHub repositories. * Integrations - #githubmarketplace gives you an essence to have multiple and competitive integrations whereas you will find less in the GitLab.

So go ahead with better understanding.

See more
AWS CodeCommit logo

AWS CodeCommit

328
193
Fully-managed source control service that makes it easy for companies to host secure and highly scalable private Git...
328
193
PROS OF AWS CODECOMMIT
  • 44
    Free private repos
  • 26
    IAM integration
  • 24
    Pay-As-You-Go Pricing
  • 20
    Amazon feels the most Secure
  • 19
    Repo data encrypted at rest
  • 11
    I can make repository by myself if I have AWS account
  • 11
    Faster deployments when using other AWS services
  • 8
    AWS CodePipeline integration
  • 6
    Codebuild integration
  • 6
    Does not support web hooks yet! :(
  • 4
    Cost Effective
  • 2
    No Git LFS! Dealbreaker for me
  • 2
    Elastic Beanstalk Integration
  • 2
    Integrated with AWS Ecosystem
  • 1
    Integration via SQS/SNS for events (replaces webhooks)
  • 1
    IAM
  • 1
    Issue tracker
  • 1
    Available in Ireland (Dublin) region
  • 1
    CodeDeploy Integration
  • 1
    CodeCommit Trigger for an AWS Lambda Function
  • 1
    Open source friendly
  • 1
    Only US Region
  • 0
    Ui
CONS OF AWS CODECOMMIT
  • 12
    UI sucks
  • 4
    SLOW
  • 3
    No Issue Tracker
  • 2
    Bad diffing/no blame
  • 2
    NO LFS support
  • 2
    No fork
  • 2
    No webhooks
  • 1
    Can't download file from UI
  • 1
    Only time based triggers
  • 0
    Accident-prone UI

related AWS CodeCommit posts

Hi, I need advice. In my project, we are using Bitbucket hosted on-prem, Jenkins, and Jira. Also, we have restrictions not to use any plugins for code review, code quality, code security, etc., with bitbucket. Now we want to migrate to AWS CodeCommit, which would mean that we can use, let's say, Amazon CodeGuru for code reviews and move to AWS CodeBuild and AWS CodePipeline for build automation in the future rather than using Jenkins.

Now I want advice on below.

  1. Is it a good idea to migrate from Bitbucket to AWS Codecommit?
  2. If we want to integrate Jira with AWS Codecommit, then how can we do this? If a developer makes any changes in Jira, then a build should be triggered automatically in AWS and create a Jira ticket if the build fails. So, how can we achieve this?
See more
Jack Graves

Docker is used to package up our applications with all of the parts they need, such as libraries and other dependencies, and enable us to ship it all out as one package. Our repositories hosted in AWS CodeCommit are automatically built by AWS CodeBuild on changes (resulting from Pull Requests being approved) and these are stored in the the EC2 Container Registry (ECR) before being approved for deployment to the Amazon EC2 Container Service in a zero-downtime, staged upgrade. We also provide development instances of our Apps, which are also hosted in Docker containers.

See more
Git logo

Git

297.6K
6.6K
Fast, scalable, distributed revision control system
297.6K
6.6K
PROS OF GIT
  • 1.4K
    Distributed version control system
  • 1.1K
    Efficient branching and merging
  • 959
    Fast
  • 845
    Open source
  • 726
    Better than svn
  • 368
    Great command-line application
  • 306
    Simple
  • 291
    Free
  • 232
    Easy to use
  • 222
    Does not require server
  • 27
    Distributed
  • 22
    Small & Fast
  • 18
    Feature based workflow
  • 15
    Staging Area
  • 13
    Most wide-spread VSC
  • 11
    Role-based codelines
  • 11
    Disposable Experimentation
  • 7
    Frictionless Context Switching
  • 6
    Data Assurance
  • 5
    Efficient
  • 4
    Just awesome
  • 3
    Github integration
  • 3
    Easy branching and merging
  • 2
    Compatible
  • 2
    Flexible
  • 2
    Possible to lose history and commits
  • 1
    Rebase supported natively; reflog; access to plumbing
  • 1
    Light
  • 1
    Team Integration
  • 1
    Fast, scalable, distributed revision control system
  • 1
    Easy
  • 1
    Flexible, easy, Safe, and fast
  • 1
    CLI is great, but the GUI tools are awesome
  • 1
    It's what you do
  • 0
    Phinx
CONS OF GIT
  • 16
    Hard to learn
  • 11
    Inconsistent command line interface
  • 9
    Easy to lose uncommitted work
  • 8
    Worst documentation ever possibly made
  • 5
    Awful merge handling
  • 3
    Unexistent preventive security flows
  • 3
    Rebase hell
  • 2
    Ironically even die-hard supporters screw up badly
  • 2
    When --force is disabled, cannot rebase
  • 1
    Doesn't scale for big data

related Git posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.6M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Tymoteusz Paul
Devops guy at X20X Development LTD · | 23 upvotes · 10M views

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
SVN (Subversion) logo

SVN (Subversion)

801
43
Enterprise-class centralized version control for the masses
801
43
PROS OF SVN (SUBVERSION)
  • 20
    Easy to use
  • 13
    Simple code versioning
  • 5
    User/Access Management
  • 3
    Complicated code versionioning by Subversion
  • 2
    Free
CONS OF SVN (SUBVERSION)
  • 7
    Branching and tagging use tons of disk space

related SVN (Subversion) posts

I use Visual Studio Code because at this time is a mature software and I can do practically everything using it.

  • It's free and open source: The project is hosted on GitHub and it’s free to download, fork, modify and contribute to the project.

  • Multi-platform: You can download binaries for different platforms, included Windows (x64), MacOS and Linux (.rpm and .deb packages)

  • LightWeight: It runs smoothly in different devices. It has an average memory and CPU usage. Starts almost immediately and it’s very stable.

  • Extended language support: Supports by default the majority of the most used languages and syntax like JavaScript, HTML, C#, Swift, Java, PHP, Python and others. Also, VS Code supports different file types associated to projects like .ini, .properties, XML and JSON files.

  • Integrated tools: Includes an integrated terminal, debugger, problem list and console output inspector. The project navigator sidebar is simple and powerful: you can manage your files and folders with ease. The command palette helps you find commands by text. The search widget has a powerful auto-complete feature to search and find your files.

  • Extensible and configurable: There are many extensions available for every language supported, including syntax highlighters, IntelliSense and code completion, and debuggers. There are also extension to manage application configuration and architecture like Docker and Jenkins.

  • Integrated with Git: You can visually manage your project repositories, pull, commit and push your changes, and easy conflict resolution.( there is support for SVN (Subversion) users by plugin)

See more
rishig
Head of Product at Zulip · | 8 upvotes · 193.1K views
Shared insights
on
GitGitSVN (Subversion)SVN (Subversion)
at

I use Git instead of SVN (Subversion) because it allows us to scale our development team. At any given time, the Zulip open source project has hundreds of open pull requests from tens of contributors, each in various stages of the pipeline. Git's workflow makes it very easy to context switch between different feature branches.

See more
Azure DevOps logo

Azure DevOps

2.7K
249
Services for teams to share code, track work, and ship software
2.7K
249
PROS OF AZURE DEVOPS
  • 56
    Complete and powerful
  • 32
    Huge extension ecosystem
  • 27
    Azure integration
  • 26
    Flexible and powerful
  • 26
    One Stop Shop For Build server, Project Mgt, CDCI
  • 15
    Everything I need. Simple and intuitive UI
  • 13
    Support Open Source
  • 8
    Integrations
  • 7
    GitHub Integration
  • 6
    Cost free for Stakeholders
  • 6
    One 4 all
  • 6
    Crap
  • 6
    Project Mgmt Features
  • 5
    Runs in the cloud
  • 3
    Agent On-Premise(Linux - Windows)
  • 2
    Aws integration
  • 2
    Link Test Cases to Stories
  • 2
    Jenkins Integration
  • 1
    GCP Integration
CONS OF AZURE DEVOPS
  • 8
    Still dependant on C# for agents
  • 5
    Half Baked
  • 5
    Many in devops disregard MS altogether
  • 4
    Not a requirements management tool
  • 4
    Jack of all trades, master of none
  • 4
    Capacity across cross functional teams not visibile
  • 3
    Poor Jenkins integration
  • 2
    Tedious for test plan/case creation
  • 1
    Switching accounts is impossible

related Azure DevOps posts

Farzad Jalali
Senior Software Architect at BerryWorld · | 8 upvotes · 432K views

Visual Studio Azure DevOps Azure Functions Azure Websites #Azure #AzureKeyVault #AzureAD #AzureApps

#Azure Cloud Since Amazon is potentially our competitor then we need a different cloud vendor, also our programmers are microsoft oriented so the choose were obviously #Azure for us.

Azure DevOps Because we need to be able to develop a neww pipeline into Azure environment ina few minutes.

Azure Kubernetes Service We already in #Azure , also need to use K8s , so let's use AKS as it's a manged Kubernetes in the #Azure

See more
Andrey Kurdyumov
Sr. Software developer · | 8 upvotes · 205K views
Shared insights
on
Azure DevOpsAzure DevOpsGitGit

I use Azure DevOps because for me it gradually walk me from private Git repositories to simplest free option for CI/CD pipelines at the time. I spend 0$ initially to manager CI/CD for my small private projects. No need to go into two different places to setup integration, once I have git repository, I could deploy projects. Right now this is not the case since CI/CD is default for me, so I use it now from memories of old good days. I'm not yet need complexity on the projects, so I don't even consider other options with "more choices". I carefully limit my set of options during development, that's why Azure DevOps (VSTS)

See more
Jira logo

Jira

61.5K
1.2K
The #1 software development tool used by agile teams to plan, track, and release great software.
61.5K
1.2K
PROS OF JIRA
  • 310
    Powerful
  • 254
    Flexible
  • 149
    Easy separation of projects
  • 113
    Run in the cloud
  • 105
    Code integration
  • 58
    Easy to use
  • 53
    Run on your own
  • 39
    Great customization
  • 39
    Easy Workflow Configuration
  • 27
    REST API
  • 12
    Great Agile Management tool
  • 7
    Integrates with virtually everything
  • 6
    Confluence
  • 6
    Complicated
  • 3
    Sentry Issues Integration
  • 2
    It's awesome
CONS OF JIRA
  • 8
    Rather expensive
  • 5
    Large memory requirement
  • 2
    Slow
  • 1
    Cloud or Datacenter only

related Jira posts

Johnny Bell

So I am a huge fan of JIRA like #massive I used it for many many years, and really loved it, used it personally and at work. I would suggest every new workplace that I worked at to switch to JIRA instead of what I was using.

When I started at #StackShare we were using a Trello #Kanban board and I was so shocked at how easy the workflow was to follow, create new tasks and get tasks QA'd and deployed. What was so great about this was it didn't come with all the complexity of JIRA. Like setting up a project, user rules etc. You are able to hit the ground running with Trello and get tasks started right away without being overwhelmed with the complexity of options in JIRA

With a few TrelloPowerUps we were easily able to add GitHub integration and storyPoints to our cards and thats all we needed to get a really nice agile workflow going.

I'm not saying that JIRA is not useful, I can see larger companies being able to use the JIRA features and have the time to go through all the complex setup to get a really good workflow going. But for smaller #Startups that want to hit the ground running Trello for me is the way to go.

In saying that what I would love Trello to implement is to allow me to create custom fields. Right now we just have a Description field. So I am adding User Stories & How To Test in the Markdown of the Description if I could have these as custom fields then my #Agile workflow would be complete.

#StackDecisionsLaunch

See more
Jakub Olan
Node.js Software Engineer · | 17 upvotes · 445.1K views

Last time we shared there information about our decision about using YouTrack over Jira actually we found much better solution that our team have loved. Linear is a minimalistic issue tracker that integrates well with Sentry, GitHub, Slack and Figma which are our basic tools. I would like to recommend checking out Linear as a potential alternative to "heavy" issue trackers, maybe at enterprises that may not work but when we're a startup that works awesome!

See more
Git Flow logo

Git Flow

95
0
A set of git extensions to provide high-level repository operations
95
0
PROS OF GIT FLOW
    Be the first to leave a pro
    CONS OF GIT FLOW
      Be the first to leave a con

      related Git Flow posts