Alternatives to jFrog logo

Alternatives to jFrog

Apache Maven, JFrog Artifactory, Jenkins, GitHub, and GitLab are the most popular alternatives and competitors to jFrog.
109
88
+ 1
0

What is jFrog and what are its top alternatives?

Host, manage and proxy artifacts using the best Docker Registry, Maven Repository, Gradle repository, NuGet repository, Ruby repository, Debian repository npm repository, Yum repository.
jFrog is a tool in the Platform as a Service category of a tech stack.

Top Alternatives to jFrog

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

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

  • Jenkins
    Jenkins

    In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project. ...

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

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

  • Docker Hub
    Docker Hub

    It is the world's easiest way to create, manage, and deliver your teams' container applications. It is the perfect home for your teams' applications. ...

  • Heroku
    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

jFrog alternatives & related posts

Apache Maven logo

Apache Maven

2.6K
1.6K
413
Apache build manager for Java projects.
2.6K
1.6K
+ 1
413
PROS OF APACHE MAVEN
  • 136
    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 · 5.5M 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
JFrog Artifactory logo

JFrog Artifactory

316
334
0
Enterprise Universal Repository Manager
316
334
+ 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 · 235.7K 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
      Jenkins logo

      Jenkins

      51.9K
      43.8K
      2.2K
      An extendable open source continuous integration server
      51.9K
      43.8K
      + 1
      2.2K
      PROS OF JENKINS
      • 521
        Hosted internally
      • 464
        Free open source
      • 315
        Great to build, deploy or launch anything async
      • 243
        Tons of integrations
      • 210
        Rich set of plugins with good documentation
      • 110
        Has support for build pipelines
      • 72
        Open source and tons of integrations
      • 65
        Easy setup
      • 62
        It is open-source
      • 54
        Workflow plugin
      • 11
        Configuration as code
      • 10
        Very powerful tool
      • 9
        Continuous Integration
      • 9
        Many Plugins
      • 8
        Git and Maven integration is better
      • 8
        Great flexibility
      • 7
        100% free and open source
      • 6
        Github integration
      • 6
        Slack Integration (plugin)
      • 5
        Easy customisation
      • 5
        Self-hosted GitLab Integration (plugin)
      • 4
        Docker support
      • 4
        Pipeline API
      • 3
        Platform idnependency
      • 3
        Excellent docker integration
      • 3
        Fast builds
      • 3
        Hosted Externally
      • 2
        Customizable
      • 2
        AWS Integration
      • 2
        It's Everywhere
      • 2
        JOBDSL
      • 2
        Can be run as a Docker container
      • 2
        It`w worked
      • 1
        Easily extendable with seamless integration
      • 1
        Build PR Branch Only
      • 1
        NodeJS Support
      • 1
        PHP Support
      • 1
        Ruby/Rails Support
      • 1
        Universal controller
      • 1
        Loose Coupling
      CONS OF JENKINS
      • 12
        Workarounds needed for basic requirements
      • 9
        Groovy with cumbersome syntax
      • 7
        Plugins compatibility issues
      • 6
        Lack of support
      • 6
        Limited abilities with declarative pipelines
      • 4
        No YAML syntax
      • 3
        Too tied to plugins versions

      related Jenkins posts

      Tymoteusz Paul
      Devops guy at X20X Development LTD · | 23 upvotes · 5.5M 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
      Thierry Schellenbach

      Releasing new versions of our services is done by Travis CI. Travis first runs our test suite. Once it passes, it publishes a new release binary to GitHub.

      Common tasks such as installing dependencies for the Go project, or building a binary are automated using plain old Makefiles. (We know, crazy old school, right?) Our binaries are compressed using UPX.

      Travis has come a long way over the past years. I used to prefer Jenkins in some cases since it was easier to debug broken builds. With the addition of the aptly named “debug build” button, Travis is now the clear winner. It’s easy to use and free for open source, with no need to maintain anything.

      #ContinuousIntegration #CodeCollaborationVersionControl

      See more
      GitHub logo

      GitHub

      238.4K
      204.1K
      10.2K
      Powerful collaboration, review, and code management for open source and private development projects
      238.4K
      204.1K
      + 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
      • 864
        Easy setup
      • 502
        Issue tracker
      • 484
        Great community
      • 480
        Remote team collaboration
      • 449
        Great way to share
      • 440
        Pull request and features planning
      • 144
        Just works
      • 131
        Integrated in many tools
      • 118
        Free Public Repos
      • 114
        Github Gists
      • 109
        Github pages
      • 82
        Easy to find repos
      • 61
        Open source
      • 59
        Easy to find projects
      • 59
        It's free
      • 56
        Network effect
      • 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
      • 22
        Clean interface and good integrations
      • 19
        Learn from others source code
      • 15
        Because: Git
      • 14
        It integrates directly with Azure
      • 9
        Standard in Open Source collab
      • 9
        Newsfeed
      • 8
        It integrates directly with Hipchat
      • 7
        Fast
      • 7
        Beautiful user experience
      • 6
        Cloud SCM
      • 6
        Easy to discover new code libraries
      • 5
        Smooth integration
      • 5
        It's awesome
      • 5
        Integrations
      • 5
        Graphs
      • 5
        Nice API
      • 4
        Quick Onboarding
      • 4
        Remarkable uptime
      • 4
        Hands down best online Git service available
      • 4
        CI Integration
      • 4
        Reliable
      • 3
        Loved by developers
      • 3
        Free HTML hosting
      • 3
        Security options
      • 3
        Simple but powerful
      • 3
        Uses GIT
      • 3
        Unlimited Public Repos at no cost
      • 3
        Version Control
      • 3
        Easy to use and collaborate with others
      • 2
        Nice to use
      • 2
        IAM
      • 2
        Ci
      • 1
        Easy and efficient maintainance of the projects
      • 1
        Good tools support
      • 1
        Beautiful
      • 1
        Free HTML hostings
      • 1
        Self Hosted
      • 1
        All in one development service
      • 1
        Easy to use
      • 1
        Easy source control and everything is backed up
      • 1
        Leads the copycats
      • 1
        Never dethroned
      • 1
        IAM integration
      • 1
        Issues tracker
      • 1
        Very Easy to Use
      • 1
        Easy deployment via SSH
      • 1
        Free private repos
      • 0
        Profound
      CONS OF GITHUB
      • 51
        Owned by micrcosoft
      • 37
        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
      • 2
        Does not have a graph for showing history like git lens
      • 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 · | 29 upvotes · 5M 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

      53K
      44.9K
      2.4K
      Open source self-hosted Git management software
      53K
      44.9K
      + 1
      2.4K
      PROS OF GITLAB
      • 501
        Self hosted
      • 428
        Free
      • 336
        Has community edition
      • 241
        Easy setup
      • 239
        Familiar interface
      • 133
        Includes many features, including ci
      • 109
        Nice UI
      • 82
        Good integration with gitlabci
      • 55
        Simple setup
      • 33
        Has an official mobile app
      • 32
        Free private repository
      • 29
        Continuous Integration
      • 20
        Open source, great ui (like github)
      • 16
        Slack Integration
      • 12
        Full CI flow
      • 10
        Free and unlimited private git repos
      • 8
        User, group, and project access management is simple
      • 7
        Intuitive UI
      • 7
        Built-in CI
      • 7
        All in one (Git, CI, Agile..)
      • 4
        Both public and private Repositories
      • 3
        Integrated Docker Registry
      • 3
        CI
      • 3
        Full DevOps suite with Git
      • 3
        It's powerful source code management tool
      • 3
        Excellent
      • 3
        Build/pipeline definition alongside code
      • 3
        Mattermost Chat client
      • 3
        Issue system
      • 3
        So easy to use
      • 2
        Because is the best remote host for git repositories
      • 2
        Dockerized
      • 2
        Free private repos
      • 2
        Great for team collaboration
      • 2
        Unlimited free repos & collaborators
      • 2
        It's fully integrated
      • 2
        I like the its runners and executors feature
      • 2
        One-click install through DigitalOcean
      • 2
        Security and Stable
      • 2
        Low maintenance cost due omnibus-deployment
      • 2
        On-premises
      • 1
        Kubernetes integration with GitLab CI
      • 1
        Multilingual interface
      • 1
        Review Apps feature
      • 1
        Powerful software planning and maintaining tools
      • 1
        Groups of groups
      • 1
        Built-in Docker Registry
      • 1
        Beautiful
      • 1
        Wounderful
      • 1
        Opensource
      • 1
        Not Microsoft Owned
      • 1
        Many private repo
      • 1
        Published IP list for whitelisting (gl-infra#434)
      • 1
        The dashboard with deployed environments
      • 1
        Powerful Continuous Integration System
      • 1
        Kubernetes Integration
      • 1
        Native CI
      • 1
        HipChat intergration
      • 1
        It includes everything I need, all packaged with docker
      • 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) · | 20 upvotes · 445.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
      Git logo

      Git

      172.3K
      147.1K
      6.6K
      Fast, scalable, distributed revision control system
      172.3K
      147.1K
      + 1
      6.6K
      PROS OF GIT
      • 1.4K
        Distributed version control system
      • 1.1K
        Efficient branching and merging
      • 960
        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
      • 7
        Worst documentation ever possibly made
      • 5
        Awful merge handling
      • 3
        Unexistent preventive security flows
      • 3
        Rebase hell
      • 2
        When --force is disabled, cannot rebase
      • 2
        Ironically even die-hard supporters screw up badly

      related Git posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 5M 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
      Ali Soueidan
      Creative Web Developer at Ali Soueidan · | 18 upvotes · 953.4K views

      Application and Data: Since my personal website ( https://alisoueidan.com ) is a SPA I've chosen to use Vue.js, as a framework to create it. After a short skeptical phase I immediately felt in love with the single file component concept! I also used vuex for state management, which makes working with several components, which are communicating with each other even more fun and convenient to use. Of course, using Vue requires using JavaScript as well, since it is the basis of it.

      For markup and style, I used Pug and Sass, since they’re the perfect match to me. I love the clean and strict syntax of both of them and even more that their structure is almost similar. Also, both of them come with an expanded functionality such as mixins, loops and so on related to their “siblings” (HTML and CSS). Both of them require nesting and prevent untidy code, which can be a huge advantage when working in teams. I used JSON to store data (since the data quantity on my website is moderate) – JSON works also good in combo with Pug, using for loops, based on the JSON Objects for example.

      To send my contact form I used PHP, since sending emails using PHP is still relatively convenient, simple and easy done.

      DevOps: Of course, I used Git to do my version management (which I even do in smaller projects like my website just have an additional backup of my code). On top of that I used GitHub since it now supports private repository for free accounts (which I am using for my own). I use Babel to use ES6 functionality such as arrow functions and so on, and still don’t losing cross browser compatibility.

      Side note: I used npm for package management. 🎉

      *Business Tools: * I use Asana to organize my project. This is a big advantage to me, even if I work alone, since “private” projects can get interrupted for some time. By using Asana I still know (even after month of not touching a project) what I’ve done, on which task I was at last working on and what still is to do. Working in Teams (for enterprise I’d take on Jira instead) of course Asana is a Tool which I really love to use as well. All the graphics on my website are SVG which I have created with Adobe Illustrator and adjusted within the SVG code or by using JavaScript or CSS (SASS).

      See more
      Docker Hub logo

      Docker Hub

      219
      240
      6
      Build and Ship any Application Anywhere
      219
      240
      + 1
      6
      PROS OF DOCKER HUB
      • 1
        Provides public and private repositories
      • 1
        Uses a very familiar collaboration model as GitHub, the
      • 1
        Quickly creates organizations, add users or create grou
      • 1
        Allows users to set permissions to restrict access or s
      • 1
        Fairly inexpensive with usage based pricing
      • 1
        Security scanning available
      CONS OF DOCKER HUB
      • 1
        Lacks fine grain access control
      • 1
        Does not provide any insight into the registry usage
      • 1
        Lacks LDAP, SAML and OAuth support

      related Docker Hub posts

      Shared insights
      on
      Amazon ECRAmazon ECRDocker HubDocker Hub

      We have been using Docker Hub free plan for some time, which had automated builds feature included in the free plan. Recently it has been removed from the free plan. Therefore we have thought to either go ahead with a paid plan of Docker Hub, which includes automated builds feature or migrate to use Amazon ECR as the container registry management solution. Since we already use some AWS services, going ahead with Amazon ECR is a viable solution. I am a bit confused as to what would be the best choice going ahead. Please advice...!

      See more
      Heroku logo

      Heroku

      23.4K
      18.7K
      3.2K
      Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
      23.4K
      18.7K
      + 1
      3.2K
      PROS OF HEROKU
      • 705
        Easy deployment
      • 459
        Free for side projects
      • 374
        Huge time-saver
      • 348
        Simple scaling
      • 261
        Low devops skills required
      • 190
        Easy setup
      • 174
        Add-ons for almost everything
      • 153
        Beginner friendly
      • 150
        Better for startups
      • 133
        Low learning curve
      • 48
        Postgres hosting
      • 41
        Easy to add collaborators
      • 30
        Faster development
      • 24
        Awesome documentation
      • 19
        Simple rollback
      • 19
        Focus on product, not deployment
      • 15
        Natural companion for rails development
      • 15
        Easy integration
      • 12
        Great customer support
      • 8
        GitHub integration
      • 6
        Painless & well documented
      • 6
        No-ops
      • 4
        I love that they make it free to launch a side project
      • 4
        Free
      • 3
        Great UI
      • 3
        Just works
      • 2
        PostgreSQL forking and following
      • 2
        MySQL extension
      • 1
        Security
      • 1
        Able to host stuff good like Discord Bot
      • 0
        Sec
      CONS OF HEROKU
      • 26
        Super expensive
      • 8
        Not a whole lot of flexibility
      • 6
        Storage
      • 6
        No usable MySQL option
      • 4
        Low performance on free tier
      • 1
        24/7 support is $1,000 per month

      related Heroku posts

      Russel Werner
      Lead Engineer at StackShare · | 32 upvotes · 1.6M views

      StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

      Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

      #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 5M 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