Continuous Delivery reviews by real, verified users. Find unbiased ratings on user satisfaction, features, and price based on the most reviews available anywhere.
Products classified in the overall Continuous Delivery category are similar in many regards and help companies of all sizes solve their business problems. However, small business features, pricing, setup, and installation differ from businesses of other sizes, which is why we match buyers to the right Small Business Continuous Delivery to fit their needs. Compare product ratings based on reviews from enterprise users or connect with one of G2's buying advisors to find the right solutions within the Small Business Continuous Delivery category.
In addition to qualifying for inclusion in the Continuous Delivery Software category, to qualify for inclusion in the Small Business Continuous Delivery Software category, a product must have at least 10 reviews left by a reviewer from a small business.
GitHub is how people build software. Millions of individuals and organizations around the world use GitHub to discover, share, and contribute to software—from games and experiments to popular frameworks and leading applications. Together, we're defining how software is built today.
GitLab is a complete open-source DevOps platform, delivered as a single application, fundamentally changing the way Development, Security, and Ops teams collaborate and build software. From idea to production, GitLab helps teams improve cycle time from weeks to minutes, reduce development process costs and decrease time to market while increasing developer productivity.
Get back your time with Buddy’s delivery pipelines that eliminate repeatable tasks in your daily development. Automatically build & ship web projects on a single git push, on click, or recurrently. Easily define your own delivery process just like you build a house of bricks: from builds and tests, to deployments, custom scripts, and website monitoring. Bring the newest tech to your team’s stack with native Docker support: containers, microservices, Kubernetes deployments, and more.
Flosum is a complete Salesforce-based Application Lifecycle Management solution that is designed for the Salesforce.com platform. Flosum manages development processes from requirements planning all the way to deployment into production. As a native Salesforce.com application, it promotes governance, compliance, and rapid innovation in the successful delivery of software. Specific features include: Governance: A deployment through Flosum keeps the auditors happy. Flosum tracks every action and
Countless mobile app developers rely on Bitrise to automate the build-, test- and deploy process for their applications, allowing for rapid iteration, better apps, faster product-market fit and overall increased productivity. With customers ranging from single person work-for-hire studios, to billion dollar enterprise companies, Bitrise has enabled the successful deployment of millions of app builds. Customer include chart-toppers like Runkeeper, Grindr, Duolingo, Just-Eat, Careem, Buffer, Sixt
CircleCI is the worlds largest shared continuous integration and continuous delivery (CI/CD) platform, and the central hub where code moves from idea to delivery. As one of the most-used DevOps tools that processes more than 1 million builds a day, CircleCI has unique access to data on how engineering teams work, and how their code runs. Companies like Spotify, Coinbase, Stitch Fix, and BuzzFeed use us to improve engineering team productivity, release better products, and get to market faster.
Our core mission at Plesk is to simplify the lives of web pros, so they can focus on their core business - not infrastructure management. Key Plesk platform features are automation and management of domains, mail accounts, web apps, programming languages and databases. Providing a ready-to-code environment and strong security across all layers and operating systems. Currently, we operate on +390k servers globally, support operations of +11 million websites & 19 million mailboxes. Check out
Semaphore is the fastest continuous integration and delivery (CI/CD) platform on the market, powering the world’s best engineering teams. Our aim is to make CI/CD practices more accessible to developers, provide a great user experience, and treat our customers as we’d like to be treated. After you push code to GitHub, it quickly runs your tests on a platform with first-class Docker, Kubernetes, iOS support and 100+ tools preinstalled. Automate any continuous delivery pipeline. Get complete cont
Build, evolve, and scale your website fleet—with zero infrastructure management investment. Get hosting, CI/CD, automated updates, global 24x7 support. And much more. For organizations that want to cost-effectively manage multiple websites or applications, Platform.sh is the end-to-end Platform-as-a-Service that enables you to build, run, and scale those sites and applications without investing time and money in infrastructure and process. Unlike traditional managed hosting or PaaS providers, P
CodeShip is a hosted Continuous Integration and Delivery platform. It sits between your source code repository (e.g. GitHub, GitLab or Bitbucket) and the hosting environment (e.g. Amazon Web Services) and automatically tests and deploys every change in your platform. Your Engineering team can focus on developing better applications instead of wasting time on maintaining a cumbersome CI server. Codeship scales with your needs, allows you to speed up your test suites and enables your developers to
Codefresh is a modern CI/CD platform designed for software development teams building & deploying cloud-native applications using Docker, Serverless, and Kubernetes. Container-based pipelines provide better flexibility, easier pipeline creation, and dozens of speed optimizations to make Codefresh the fastest CI/CD on the planet. With open support for Linux, Windows, Arm, and Mac OS (beta), as well as advanced deployment capabilities such as Canary, Blue/Green, etc, Codefresh can support any
Gearset is the world-leading Salesforce DevOps solution, trusted by Salesforce teams of all sizes. From the Fortune 500 and FTSE 100, to startups across the world, Gearset is the release management tool of choice for companies building on Salesforce. With Gearset’s complete suite of cutting-edge Salesforce DevOps features, we’re helping businesses release 10x faster, and deliver value to their customers quicker than ever before. Built on over a decade’s experience in deployment best practice, G
Red Hat Ansible Automation Platform is a simple way to automate apps and infrastructure. Application Deployment + Configuration Management + Continuous Delivery.
Founded in 2012, Octopus Deploy enables happy deployments at over 25,000 companies around the world. Prior to Octopus Deploy, release orchestration and DevOps automation tools were clunky, limited to large enterprises and didn't deliver what they promised. Octopus Deploy was the first release automation tool to gain popular adoption by software teams, and we continue to invent new ways for Dev & Ops teams to automate releases and deliver working software to production. Octopus Deploy is a
Copado is the #1 Native DevOps Platform for Salesforce. We enable faster, error-free digital and cloud deployments and upgrades with continuous integration (CI) and continuous deployment (CD) technologies and agile cloud release management, all via an enterprise-class developer platform that is 100% native and fully integrated with Salesforce DX and Salesforce Clouds. With Copado, enterprises get a single solution with which, all key DevOps functions and processes are seamlessly integrated, manu
TeamCity will make sure your software gets built, tested, and deployed, and you get notified about that appropriately, in any way you choose. It’s a continuous integration and deployment server from JetBrains which takes moments to set up, shows your build results on-the-fly, and works out of the box. And best of all – it’s free by default.
Continuous Integration for the Enterprise built on the most widely used automation server in the world - Jenkins™. CloudBees CI (Core) provides flexible, governed, powerful CI/CD you can trust. CloudBees CI is a fully-featured, cloud native solution that can be hosted on-premise or in the public cloud used to deliver CI at scale. It provides a shared, centrally managed, self-service experience for all your development teams running Jenkins. CloudBees CI on modern cloud platforms is designed to
Continuous delivery refers to the process of constantly generating deployment-ready code via agile workflows and the quick, efficient automation of repetitive tasks. Continuous delivery tools facilitate this process, enabling development teams to achieve a true DevOps environment. DevOps emerged as the result of companies’ desire to shorten the software development lifecycle. The goal behind DevOps is to create a more responsive development, update, and upkeep strategy, as well as to keep development objectives in constant alignment with business ones. Continuous integration, continuous delivery, and continuous deployment were created to promote more agile strategies on the development side. The theory behind each are as follows:
Continuous integration: Merging all developers’ code into one central repository at regular intervals to avoid code conflicts
Continuous delivery: Keeping code constantly ready for deployment
Continuous deployment: Automatically pushing code updates into production after successfully passing testing
Often, the term CI/CD is used to mean continuous integration/continuous delivery, ignoring continuous deployment, because continuous deployment has become antiquated and exists instead as part of the continuous delivery umbrella. Continuous delivery software facilitates the maintenance of tested and approved code in a deployment-ready state. Once the approved code is ready for deployment, the key lies in whether that code is deployed automatically (continuous deployment) or manually. Continuous deployment necessitates more rigorous testing to ensure nothing broken gets pushed into production, and the potential that bad code can go live is discouraging. Not all continuous delivery solutions include continuous deployment, so companies seeking to avoid the potential pitfalls of continuous deployment should assess their options to ensure the possibility of manual deployment. Regardless, continuous delivery serves up a huge advantage in the form of faster software updates and more responsive upkeep, allowing businesses to remain as competitive as possible.
Key Benefits of Continuous Delivery Software
While continuous delivery can sound intimidating to a lot of companies, the strategy can be quite beneficial. Continuous delivery—in conjunction with continuous integration—creates a strong, fluid pipeline of unified code production, testing, and distribution. Instead of worrying about intermittent, large updates, companies can quickly crank out small changes to continuously improve their software.
Huge update deployments tend to be painful to release, hectic to track, and difficult to sift through for both businesses and consumers. Continuous delivery strategies allow small, incremental changes that are easier to track (especially in conjunction with configuration management software), troubleshoot, and roll back in the event of a break. Incremental changes are also much faster to redeploy, which saves the effort of going through manual deployment over and over.
Fast feedback cycle — Most continuous delivery software enables deployments to occur automatically once functional testing is successful, meaning businesses get quicker feedback around ideas and changes made to their products. Users will have access to changes as soon as they’re ready, which helps businesses keep a consistent stream of feedback on their product. This helps companies build stronger products in the long run.
Competitive edge — Taking long spans between software updates or add-on releases leaves businesses vulnerable to being overtaken by more agile, responsive companies. With continuous delivery software, the business can keep updates and constructive changes flowing directly into the production environment, resulting in a stronger, more consistent product.
Development (specifically DevOps) teams are the primary users of continuous delivery tools. Software engineers and development team leads, both get a lot of value from these tools, albeit for different reasons. Developers easily launch changes directly into pre- and post-production environments with continuous delivery software, which saves them time. Team leads and managers get a lot of use out of the reports, metrics, and dashboards many of these solutions offer, as they provide higher-level insights into the progress the development teams are making.
The following are the most common features seen in continuous delivery solutions:
Repository connectivity — Continuous delivery software needs access to code repositories to push successfully tested code into production. This software should have the capability to connect with any of a business’ code repositories, automatically passing successfully tested code into preproduction or live product updates.
Deployment-ready staging — Continuous delivery software automatically maintains code in a deployment-ready state. This allows developers to stage their code more quickly and efficiently, and empowers businesses to make changes to their software on the fly as issues or market changes arise.
Role-based task assignment — Beyond the outright automation of tasks, continuous delivery software designates the necessary tasks and workflows for a team's unique development cycle. This task designation is role based and fully customizable so that development teams are able to build the delivery pipeline that works best for them.
Continuous deployment — Most continuous delivery software allows continuous deployment or automated deployment. Continuous deployment allows companies to push small changes quickly into production, reducing the overall hassle of releasing updates and allowing development teams to focus more on writing quality code.
Deployment tracking — Keeping track of automatic code deployments help teams understand exactly why certain shifts occur, like an increase in user errors or an increase in product use. Continuous delivery software should document each code push that gets sent to production, allowing users to see exactly how the new code performs. It also shows development teams if a build fails to push to production, which will alert them to a potential issue in the code itself.
Reporting and metrics — At a higher level, continuous delivery tools should display push metadata, such as how many deployments are going out in a certain time span, what part of a software solution the deployments are targeting, and more. This feature is particularly useful for managers and team leads since reporting and metrics features give them a top-down view of a development team’s performance.
Deployment rollback — This feature is helpful when development teams hit a problem that testing failed to catch. Some continuous deployment solutions have rollback capabilities, where live code can be restored to prerollout status. This lets development teams work out what went wrong, providing additional insights that can be used for improving predeployment testing.
Pushing bad code — The fault of this issue lies less with the actual continuous delivery solution and more with a business’ testing practices and test automation. Bad code—code that causes errors, breaks, or crashes—should be caught during the testing process so that it doesn’t create problems in the production environment. If testing practices aren’t strong, continuous delivery solutions end up pushing that bad code into staging and production, which taints the user experience. When implementing a continuous delivery solution, especially one with continuous deployment, it is important for a company to have strong manual and automated tests to catch any bad code before it goes live.
Pushing too many visible changes — Companies, when using continuous delivery as part of their development process, should keep in mind the effect it may have on their user base if visible changes or updates keep appearing every few days or each week. While changes to currently existing issues are often welcome, users may start getting concerned if they keep receiving visual or functional changes at small increments. Consistency is key to both improving the learning curve and maintaining customer happiness, and when a company messes with consistency too much or too often, it risks upsetting its users. Generally, a company will want to avoid doing too many noticeable changes too close together, unless those changes are paired with formally released information to update users about the nature and reasons for the changes.