Alternatives to fastlane logo

Alternatives to fastlane

HockeyApp, Bitrise, Jenkins, Firebase, and CircleCI are the most popular alternatives and competitors to fastlane.
653
74

What is fastlane and what are its top alternatives?

fastlane lets you define and run your deployment pipelines for different environments. It helps you unify your app’s release process and automate the whole process. fastlane connects all fastlane tools and third party tools, like CocoaPods.
fastlane is a tool in the Mobile Continuous Integration category of a tech stack.
fastlane is an open source tool with 39.6K GitHub stars and 5.7K GitHub forks. Here’s a link to fastlane's open source repository on GitHub

Top Alternatives to fastlane

  • HockeyApp
    HockeyApp

    HockeyApp is the best way to collect live crash reports, get feedback from your users, distribute your betas, and analyze your test coverage. ...

  • Bitrise
    Bitrise

    It is a Continous Integration and Delivery (CI/CD) Platform as a Service (PaaS) with a main focus on mobile app development (iOS, Android). You can automate the testing and deployment of your apps with just a few clicks. When you trigger a build a Virtual Machine is assigned to host your build and your defined Workflow (series of Steps scripts) will be executed, step by step. ...

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

  • Firebase
    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • CircleCI
    CircleCI

    Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp. ...

  • TestFlight
    TestFlight

    With TestFlight, developers simply upload a build, and the testers can install it directly from their device, over the air. ...

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

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

fastlane alternatives & related posts

HockeyApp logo

HockeyApp

168
158
38
Manage your betas and collect live crash reports for iOS, Android, Windows Phone, and OS X apps.
168
158
+ 1
38
PROS OF HOCKEYAPP
  • 17
    Crash analytics
  • 11
    Cross-platform
  • 5
    Mobile application distribution
  • 2
    JIRA Integration
  • 2
    Open source
  • 1
    GitHub Integration
CONS OF HOCKEYAPP
    Be the first to leave a con

    related HockeyApp posts

    Bitrise logo

    Bitrise

    339
    369
    74
    Automate your mobile app development from building through testing to deployment
    339
    369
    + 1
    74
    PROS OF BITRISE
    • 18
      Easy setup
    • 9
      Bitbucket Integration
    • 8
      Advanced Workflow configuration
    • 7
      Slack integration
    • 7
      Github Integration
    • 5
      Great tools for iOS and Android development
    • 5
      Friendly & Easy to use
    • 4
      Great support
    • 3
      Pricing by concurrency, not team size
    • 2
      Fast Updates
    • 2
      Discounts for contributors
    • 2
      Open Source
    • 1
      Fast Builds
    • 1
      Developer centric
    CONS OF BITRISE
      Be the first to leave a con

      related Bitrise posts

      Jesus Dario Rivera Rubio
      Telecomm Engineering at Netbeast · | 10 upvotes · 1.2M views

      We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

      Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

      We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

      You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

      See more

      Dear Community!

      I am researching for Mobile Application Management platform for managing android and ios release management in Fintech space. I see following options are good:

      Please suggest if you have better option.

      See more
      Jenkins logo

      Jenkins

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

      related Jenkins posts

      Tymoteusz Paul
      Devops guy at X20X Development LTD · | 23 upvotes · 9.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
      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
      Firebase logo

      Firebase

      40.9K
      35.1K
      2K
      The Realtime App Platform
      40.9K
      35.1K
      + 1
      2K
      PROS OF FIREBASE
      • 371
        Realtime backend made easy
      • 270
        Fast and responsive
      • 242
        Easy setup
      • 215
        Real-time
      • 191
        JSON
      • 134
        Free
      • 128
        Backed by google
      • 83
        Angular adaptor
      • 68
        Reliable
      • 36
        Great customer support
      • 32
        Great documentation
      • 25
        Real-time synchronization
      • 21
        Mobile friendly
      • 19
        Rapid prototyping
      • 14
        Great security
      • 12
        Automatic scaling
      • 11
        Freakingly awesome
      • 8
        Super fast development
      • 8
        Angularfire is an amazing addition!
      • 8
        Chat
      • 6
        Firebase hosting
      • 6
        Built in user auth/oauth
      • 6
        Awesome next-gen backend
      • 6
        Ios adaptor
      • 4
        Speed of light
      • 4
        Very easy to use
      • 3
        Great
      • 3
        It's made development super fast
      • 3
        Brilliant for startups
      • 2
        Free hosting
      • 2
        Cloud functions
      • 2
        JS Offline and Sync suport
      • 2
        Low battery consumption
      • 2
        .net
      • 2
        The concurrent updates create a great experience
      • 2
        Push notification
      • 2
        I can quickly create static web apps with no backend
      • 2
        Great all-round functionality
      • 2
        Free authentication solution
      • 1
        Easy Reactjs integration
      • 1
        Google's support
      • 1
        Free SSL
      • 1
        CDN & cache out of the box
      • 1
        Easy to use
      • 1
        Large
      • 1
        Faster workflow
      • 1
        Serverless
      • 1
        Good Free Limits
      • 1
        Simple and easy
      CONS OF FIREBASE
      • 31
        Can become expensive
      • 16
        No open source, you depend on external company
      • 15
        Scalability is not infinite
      • 9
        Not Flexible Enough
      • 7
        Cant filter queries
      • 3
        Very unstable server
      • 3
        No Relational Data
      • 2
        Too many errors
      • 2
        No offline sync

      related Firebase posts

      Stephen Gheysens
      Lead Solutions Engineer at Inscribe · | 14 upvotes · 1.8M views

      Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

      My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

      See more
      Eugene Cheah

      For inboxkitten.com, an opensource disposable email service;

      We migrated our serverless workload from Cloud Functions for Firebase to CloudFlare workers, taking advantage of the lower cost and faster-performing edge computing of Cloudflare network. Made possible due to our extremely low CPU and RAM overhead of our serverless functions.

      If I were to summarize the limitation of Cloudflare (as oppose to firebase/gcp functions), it would be ...

      1. <5ms CPU time limit
      2. Incompatible with express.js
      3. one script limitation per domain

      Limitations our workload is able to conform with (YMMV)

      For hosting of static files, we migrated from Firebase to CommonsHost

      More details on the trade-off in between both serverless providers is in the article

      See more
      CircleCI logo

      CircleCI

      12.8K
      7.1K
      974
      Automate your development process quickly, safely, and at scale
      12.8K
      7.1K
      + 1
      974
      PROS OF CIRCLECI
      • 226
        Github integration
      • 177
        Easy setup
      • 153
        Fast builds
      • 94
        Competitively priced
      • 74
        Slack integration
      • 55
        Docker support
      • 45
        Awesome UI
      • 33
        Great customer support
      • 18
        Ios support
      • 14
        Hipchat integration
      • 13
        SSH debug access
      • 11
        Free for Open Source
      • 6
        Mobile support
      • 5
        Nodejs support
      • 5
        Bitbucket integration
      • 5
        YAML configuration
      • 4
        AWS CodeDeploy integration
      • 3
        Free for Github private repo
      • 3
        Great support
      • 2
        Clojurescript
      • 2
        Continuous Deployment
      • 2
        Parallelism
      • 2
        Clojure
      • 2
        OSX support
      • 2
        Simple, clean UI
      • 1
        Unstable
      • 1
        Ci
      • 1
        Favorite
      • 1
        Helpful documentation
      • 1
        Autoscaling
      • 1
        Extremely configurable
      • 1
        Works
      • 1
        Android support
      • 1
        Fair pricing
      • 1
        All inclusive testing
      • 1
        Japanese in rspec comment appears OK
      • 1
        Build PR Branch Only
      • 1
        So circular
      • 1
        Easy setup, easy to understand, fast and reliable
      • 1
        Parallel builds for slow test suites
      • 1
        Easy setup. 2.0 is fast!
      • 1
        Easy to deploy to private servers
      • 1
        Really easy to use
      • 0
        Stable
      CONS OF CIRCLECI
      • 12
        Unstable
      • 6
        Scammy pricing structure
      • 0
        Aggressive Github permissions

      related CircleCI posts

      Russel Werner
      Lead Engineer at StackShare · | 32 upvotes · 2.8M 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 · | 30 upvotes · 11M 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
      TestFlight logo

      TestFlight

      1.1K
      703
      163
      iOS beta testing on the fly.
      1.1K
      703
      + 1
      163
      PROS OF TESTFLIGHT
      • 62
        Must have for ios development
      • 49
        Beta testing
      • 20
        Easy setup
      • 10
        Easy way to push out updates for internal testers
      • 7
        In-App Updates
      • 5
        Crash Logging
      • 4
        Checkpoints
      • 3
        Multiple platforms
      • 2
        Remote Logging
      • 1
        Sessions
      CONS OF TESTFLIGHT
        Be the first to leave a con

        related TestFlight posts

        Utkarsh Mehta
        Senior Blockchain Developer · | 1 upvote · 5.3K views

        I created microservices with Kafka for message queue, Meteor for app development with JavaScript & TestFlight for iOS app development, Elasticsearch for logging SendGrid for automated mails. Git & GitHub for SCM.

        See more
        Git logo

        Git

        296.9K
        178.2K
        6.6K
        Fast, scalable, distributed revision control system
        296.9K
        178.2K
        + 1
        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 · 11M 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 · 9.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
        GitHub logo

        GitHub

        285.1K
        249K
        10.3K
        Powerful collaboration, review, and code management for open source and private development projects
        285.1K
        249K
        + 1
        10.3K
        PROS OF GITHUB
        • 1.8K
          Open source friendly
        • 1.5K
          Easy source control
        • 1.3K
          Nice UI
        • 1.1K
          Great for team collaboration
        • 867
          Easy setup
        • 504
          Issue tracker
        • 487
          Great community
        • 483
          Remote team collaboration
        • 449
          Great way to share
        • 442
          Pull request and features planning
        • 147
          Just works
        • 132
          Integrated in many tools
        • 122
          Free Public Repos
        • 116
          Github Gists
        • 113
          Github pages
        • 83
          Easy to find repos
        • 62
          Open source
        • 60
          Easy to find projects
        • 60
          It's free
        • 56
          Network effect
        • 49
          Extensive API
        • 43
          Organizations
        • 42
          Branching
        • 34
          Developer Profiles
        • 32
          Git Powered Wikis
        • 30
          Great for collaboration
        • 24
          It's fun
        • 23
          Clean interface and good integrations
        • 22
          Community SDK involvement
        • 20
          Learn from others source code
        • 16
          Because: Git
        • 14
          It integrates directly with Azure
        • 10
          Standard in Open Source collab
        • 10
          Newsfeed
        • 8
          Fast
        • 8
          Beautiful user experience
        • 8
          It integrates directly with Hipchat
        • 7
          Easy to discover new code libraries
        • 6
          Smooth integration
        • 6
          Integrations
        • 6
          Graphs
        • 6
          Nice API
        • 6
          It's awesome
        • 6
          Cloud SCM
        • 5
          Quick Onboarding
        • 5
          Remarkable uptime
        • 5
          CI Integration
        • 5
          Reliable
        • 5
          Hands down best online Git service available
        • 4
          Version Control
        • 4
          Unlimited Public Repos at no cost
        • 4
          Simple but powerful
        • 4
          Loved by developers
        • 4
          Free HTML hosting
        • 4
          Uses GIT
        • 4
          Security options
        • 4
          Easy to use and collaborate with others
        • 3
          Easy deployment via SSH
        • 3
          Ci
        • 3
          IAM
        • 3
          Nice to use
        • 2
          Easy and efficient maintainance of the projects
        • 2
          Beautiful
        • 2
          Self Hosted
        • 2
          Issues tracker
        • 2
          Easy source control and everything is backed up
        • 2
          Never dethroned
        • 2
          All in one development service
        • 2
          Good tools support
        • 2
          Free HTML hostings
        • 2
          IAM integration
        • 2
          Very Easy to Use
        • 2
          Easy to use
        • 2
          Leads the copycats
        • 2
          Free private repos
        • 1
          Profound
        • 1
          Dasf
        CONS OF GITHUB
        • 55
          Owned by micrcosoft
        • 38
          Expensive for lone developers that want private repos
        • 15
          Relatively slow product/feature release cadence
        • 10
          API scoping could be better
        • 9
          Only 3 collaborators for private repos
        • 4
          Limited featureset for issue management
        • 3
          Does not have a graph for showing history like git lens
        • 2
          GitHub Packages does not support SNAPSHOT versions
        • 1
          No multilingual interface
        • 1
          Takes a long time to commit
        • 1
          Expensive

        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

        Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.

        Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!

        Check Out My Architecture: CLICK ME

        Check out the GitHub repo attached

        See more