Alternatives to BinTray logo

Alternatives to BinTray

JitPack, JFrog Artifactory, Apache Maven, GitHub, and GitLab are the most popular alternatives and competitors to BinTray.
53
57
+ 1
24

What is BinTray and what are its top alternatives?

Bintray offers developers the fastest way to publish and consume OSS software releases. With Bintray's full self-service platform developers have full control over their published software and how it is distributed to the world.
BinTray is a tool in the Code Collaboration & Version Control category of a tech stack.

Top Alternatives to BinTray

  • JitPack

    JitPack

    JitPack is an easy to use package repository for Gradle/Sbt and Maven projects. We build GitHub projects on demand and provides ready-to-use packages. ...

  • JFrog Artifactory

    JFrog Artifactory

    It integrates with your existing ecosystem supporting end-to-end binary management that overcomes the complexity of working with different software package management systems, and provides consistency to your CI/CD workflow. ...

  • Apache Maven

    Apache Maven

    Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects. ...

  • GitHub

    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

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

  • GitHub Enterprise

    GitHub Enterprise

    GitHub Enterprise lets developers use the tools they love across the development process with support for popular IDEs, continuous integration tools, and hundreds of third party apps and services. ...

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

BinTray alternatives & related posts

JitPack logo

JitPack

32
61
11
JitPack builds GitHub Gradle and Maven projects on demand and provides ready-to-use packages
32
61
+ 1
11
PROS OF JITPACK
  • 11
    Because uploading to maven central is a ball ache
CONS OF JITPACK
    Be the first to leave a con

    related JitPack posts

    JFrog Artifactory logo

    JFrog Artifactory

    267
    278
    0
    Enterprise Universal Repository Manager
    267
    278
    + 1
    0
    PROS OF JFROG ARTIFACTORY
      Be the first to leave a pro
      CONS OF JFROG ARTIFACTORY
        Be the first to leave a con

        related JFrog Artifactory posts

        Joshua Dean Küpper
        CEO at Scrayos UG (haftungsbeschränkt) · | 10 upvotes · 179.3K views

        We use Sonatype Nexus to store our closed-source java libraries to simplify our deployment and dependency-management. While there are many alternatives, most of them are expensive ( GitLab Enterprise ), monilithic ( JFrog Artifactory ) or only offer SaaS-licences. We preferred the on-premise approach of Nexus and therefore decided to use it.

        We exclusively use the Maven-capabilities and are glad that the modular design of Nexus allows us to run it very lightweight.

        See more

        Whenever Qualys scan finds out software vulnerability, say for example Java SDK or any software version that has a potential vulnerability, we search the web to find out the solution and usually install a later version or patch downloading from the web. The problem is, as we are downloading it from web and there are a number of servers where we patch and as an ultimate outcome different people downloads different version and so forth. So I want to create a repository for such binaries so that we use the same patch for all servers.

        When I was thinking about the repo, obviously first thought came as GitHub.. But then I realized, it is for code version control and collaboration, not for the packaged software. The other option I am thinking is JFrog Artifactory which stores the binaries and the package software.

        What is your recommendation?

        See more
        Apache Maven logo

        Apache Maven

        2.2K
        1.4K
        414
        Apache build manager for Java projects.
        2.2K
        1.4K
        + 1
        414
        PROS OF APACHE MAVEN
        • 137
          Dependency management
        • 71
          Necessary evil
        • 60
          I’d rather code my app, not my build
        • 48
          Publishing packaged artifacts
        • 43
          Convention over configuration
        • 18
          Modularisation
        • 11
          Consistency across builds
        • 6
          Prevents overengineering using scripting
        • 4
          Runs Tests
        • 4
          Lot of cool plugins
        • 3
          Extensible
        • 2
          Hard to customize
        • 2
          Runs on Linux
        • 1
          Runs on OS X
        • 1
          Slow incremental build
        • 1
          Inconsistent buillds
        • 1
          Undeterminisc
        • 1
          Good IDE tooling
        CONS OF APACHE MAVEN
        • 6
          Complex
        • 1
          Inconsistent buillds
        • 0
          Not many plugin-alternatives

        related Apache Maven posts

        Tymoteusz Paul
        Devops guy at X20X Development LTD · | 23 upvotes · 4.7M 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
        Shared insights
        on
        Apache MavenApache MavenGradleGradle
        at

        We use Apache Maven because it is a standard. Gradle is very good alternative, but Gradle doesn't provide any advantage for our project. Gradle is slower (without running daemon), need more resources and a learning curve is quite big. Our project can not use a great flexibility of Gradle. On the other hand, Maven is well-know tool integrated in many IDEs, Dockers and so on.

        See more
        GitHub logo

        GitHub

        189.3K
        155.9K
        10.2K
        Powerful collaboration, review, and code management for open source and private development projects
        189.3K
        155.9K
        + 1
        10.2K
        PROS OF GITHUB
        • 1.8K
          Open source friendly
        • 1.5K
          Easy source control
        • 1.2K
          Nice UI
        • 1.1K
          Great for team collaboration
        • 861
          Easy setup
        • 502
          Issue tracker
        • 484
          Great community
        • 480
          Remote team collaboration
        • 448
          Great way to share
        • 441
          Pull request and features planning
        • 144
          Just works
        • 130
          Integrated in many tools
        • 117
          Free Public Repos
        • 111
          Github Gists
        • 108
          Github pages
        • 81
          Easy to find repos
        • 60
          Open source
        • 58
          Easy to find projects
        • 56
          Network effect
        • 56
          It's free
        • 48
          Extensive API
        • 42
          Organizations
        • 41
          Branching
        • 33
          Developer Profiles
        • 32
          Git Powered Wikis
        • 29
          Great for collaboration
        • 23
          It's fun
        • 22
          Community SDK involvement
        • 21
          Clean interface and good integrations
        • 19
          Learn from others source code
        • 14
          It integrates directly with Azure
        • 14
          Because: Git
        • 13
          Wide acceptance
        • 10
          Large community
        • 9
          Newsfeed
        • 9
          Standard in Open Source collab
        • 8
          It integrates directly with Hipchat
        • 7
          Beautiful user experience
        • 7
          Fast
        • 6
          Easy to discover new code libraries
        • 6
          Cloud SCM
        • 5
          Graphs
        • 5
          Smooth integration
        • 5
          Nice API
        • 5
          Integrations
        • 5
          It's awesome
        • 4
          Remarkable uptime
        • 4
          Hands down best online Git service available
        • 4
          Reliable
        • 3
          Easy to use and collaborate with others
        • 3
          CI Integration
        • 3
          Free HTML hosting
        • 3
          Loved by developers
        • 3
          Quick Onboarding
        • 3
          Security options
        • 3
          Simple but powerful
        • 3
          Uses GIT
        • 3
          Unlimited Public Repos at no cost
        • 3
          Version Control
        • 2
          Nice to use
        • 1
          Free private repos
        • 1
          Easy deployment via SSH
        • 1
          Beautiful
        • 1
          Owned by micrcosoft
        • 1
          Free HTML hostings
        • 1
          Self Hosted
        • 1
          All in one development service
        • 1
          Easy to use
        • 1
          Good tools support
        • 1
          Easy source control and everything is backed up
        • 1
          Leads the copycats
        • 1
          Never dethroned
        • 1
          Ci
        • 1
          Issues tracker
        • 1
          Easy and efficient maintainance of the projects
        • 1
          IAM
        • 1
          IAM integration
        • 0
          Profound
        • 0
          1
        CONS OF GITHUB
        • 46
          Owned by micrcosoft
        • 36
          Expensive for lone developers that want private repos
        • 15
          Relatively slow product/feature release cadence
        • 10
          API scoping could be better
        • 8
          Only 3 collaborators for private repos
        • 3
          Limited featureset for issue management
        • 2
          GitHub Packages does not support SNAPSHOT versions
        • 1
          Have to use a token for the package registry
        • 1
          No multilingual interface
        • 1
          Takes a long time to commit

        related GitHub posts

        Johnny Bell

        I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

        I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

        I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

        Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

        Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

        With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

        If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

        See more
        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.3M 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
        GitLab logo

        GitLab

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

        31.9K
        24.9K
        2.8K
        One place to plan projects, collaborate on code, test and deploy, all with free private repositories
        31.9K
        24.9K
        + 1
        2.8K
        PROS OF BITBUCKET
        • 905
          Free private repos
        • 398
          Simple setup
        • 347
          Nice ui and tools
        • 341
          Unlimited private repositories
        • 240
          Affordable git hosting
        • 123
          Integrates with many apis and services
        • 119
          Reliable uptime
        • 86
          Nice gui
        • 84
          Pull requests and code reviews
        • 58
          Very customisable
        • 16
          Mercurial repositories
        • 14
          SourceTree integration
        • 11
          JIRA integration
        • 10
          Track every commit to an issue in JIRA
        • 8
          Best free alternative to Github
        • 8
          Deployment hooks
        • 7
          Automatically share repositories with all your teammates
        • 7
          Compatible with Mac and Windows
        • 6
          Source Code Insight
        • 5
          Price
        • 5
          Login with Google
        • 5
          Create a wiki
        • 5
          Approve pull request button
        • 4
          Customizable pipelines
        • 4
          #2 Atlassian Product after JIRA
        • 3
          Continuous Integration and Delivery
        • 3
          Unlimited Private Repos at no cost
        • 3
          Also supports Mercurial
        • 2
          Teamcity
        • 2
          Mercurial Support
        • 2
          IAM
        • 2
          Issues tracker
        • 2
          Open source friendly
        • 2
          Multilingual interface
        • 2
          Academic license program
        • 2
          IAM integration
        • 0
          Free Private Repositories
        CONS OF BITBUCKET
        • 19
          Not much community activity
        • 17
          Difficult to review prs because of confusing ui
        • 14
          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 · 629.4K 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
        GitHub Enterprise logo

        GitHub Enterprise

        482
        550
        8
        The on-premises version of GitHub, which you can deploy and manage in your own, secure environment
        482
        550
        + 1
        8
        PROS OF GITHUB ENTERPRISE
        • 2
          Code security
        • 2
          CDCI with Github Actions
        • 2
          Expensive - $$$
        • 1
          Both Cloud and Enterprise Server Versions available
        • 1
          Draft Pull Request
        CONS OF GITHUB ENTERPRISE
        • 1
          $$$

        related GitHub Enterprise posts

        Matanel Crown
        Software Developer at BBT.live · | 7 upvotes · 66.5K views

        Hi all,

        I would like some information regarding the benefits an aspiring start-up company may have, while using GitHub Enterprise vs the regular GitHub package. On a separate issue, I'd like to understand whether GitLab may have some DevOps-related advantages GitHub does not.

        Thank you in advance, Matt

        See more
        Eric Seibert
        DevOps at Children's Hospital of Philadelphia · | 6 upvotes · 119.9K views

        We are using a Bitbucket server, and due to migration efforts and new Atlassian community license changes, we need to move to a new self-hosted solution. The new data-center license for Atlassian, available in February, will be community provisioned (free). Along with that community license, other technologies will be coming with it (Crucible, Confluence, and Jira). Is there value in a paid-for license to get the GitHub Enterprise? Are the tools that come with it worth the cost?

        I know it is about $20 per 10 seats, and we have about 300 users. Have other convertees to Microsoft's tools found it easy to do a migration? Is the toolset that much more beneficial to the free suite that one can get from Atlassian?

        So far, free seems to be the winner, and the familiarization with Atlassian implementation and maintenance is understood. Going to GitHub, are there any distinct challenges to be found or any perks to be attained?

        See more
        AWS CodeCommit logo

        AWS CodeCommit

        294
        662
        188
        Fully-managed source control service that makes it easy for companies to host secure and highly scalable private Git...
        294
        662
        + 1
        188
        PROS OF AWS CODECOMMIT
        • 43
          Free private repos
        • 26
          IAM integration
        • 23
          Pay-As-You-Go Pricing
        • 19
          Amazon feels the most Secure
        • 18
          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
        • 7
          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
          Only US Region
        • 1
          Issue tracker
        • 1
          Open source friendly
        • 1
          Available in Ireland (Dublin) region
        • 1
          CodeDeploy Integration
        • 1
          CodeCommit Trigger for an AWS Lambda Function
        • 1
          Integration via SQS/SNS for events (replaces webhooks)
        • 1
          IAM
        • 0
          Ui
        CONS OF AWS CODECOMMIT
        • 11
          UI sucks
        • 4
          SLOW
        • 3
          No Issue Tracker
        • 2
          Bad diffing/no blame
        • 2
          No fork
        • 2
          No webhooks
        • 2
          NO LFS support
        • 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

        Mojolicious Perl Redmine Redis AWS CodeCommit Amazon SES PostgreSQL Postman Docker jQuery VirtualBox Sublime Text GitHub Git GitLab CI @DBIx::Class @metacpan @TheBat

        See more