Open Source CI/CD Tools
Sort By:
CI/CD Tools
View 112 business solutionsBrowse free open source CI/CD tools and projects below. Use the toggles on the left to filter open source CI/CD tools by OS, license, language, programming language, and project status.
-
$300 Free Credits to Build on Google CloudPut your $300 in credit toward real workloads, then keep building with free monthly usage for 20+ products. No commitment and no charge until you upgrade.
-
Ship Agents FasterGemini Enterprise Agent Platform lets you rapidly build, scale, govern and optimize production-ready agents grounded in your organization's data. The platform enables developers to build custom or pre-built agents for virtually any use case. New customers get $300 in free credits.
-
1
Vercel
Optimal workflow for frontend teams
Vercel combines the best developer experience with an obsessive focus on end-user performance. Our platform enables frontend teams to do their best work. Developers love Next.js, the open source React framework Vercel built together with Google and Facebook. Next.js powers the biggest websites like Twilio, for use cases in e-commerce, travel, news, and marketing. Vercel is the best place to deploy any frontend app. Start by deploying with zero configuration to our global edge network. Scale dynamically to millions of pages without breaking a sweat. Frontend development is not meant to be a solo activity. The Vercel platform makes it a collaborative experience with deploy previews for every code change, by seamlessly integrating with GitHub, GitLab, and Bitbucket. Avoid surprises by iterating with your entire team. Test from the perspective of your users, on every platform. -
2
JUnit 5
Programmer-friendly testing framework for Java and the JVM
The 5th major version of the programmer-friendly testing framework for Java and the JVM. JUnit 5 is the next generation of JUnit. The goal is to create an up-to-date foundation for developer-side testing on the JVM. This includes focusing on Java 8 and above, as well as enabling many different styles of testing. Official CI build server for JUnit 5. Used to perform quick checks on submitted pull requests and for build matrices including the latest released OpenJDK and early access builds of the next OpenJDK. The JUnit Platform serves as a foundation for launching testing frameworks on the JVM. It also defines the TestEngine API for developing a testing framework that runs on the platform. Furthermore, the platform provides a Console Launcher to launch the platform from the command line and the JUnit Platform Suite Engine for running a custom test suite using one or more test engines on the platform. First-class support for the JUnit Platform also exists in popular IDEs. -
3
Insomnia API Client
The open-source, cross-platform API client for GraphQL
Insomnia is an open-source, cross-platform API client for GraphQL, REST, and gRPC. Deliver high-quality APIs through standards and collaboration with the Insomnia API design platform. There is a reason developers love Insomnia. With our streamlined API client, you can quickly and easily send REST, SOAP, GraphQL, and GRPC requests directly within Insomnia. Accelerate your teams through spec-driven design-first API development. Catch issues earlier, centralize standards, and adopt an API workflow that works with your existing tools. Automate manual API tests and integrate with your CI/CD process to build out an API testing pipeline using Insomnia Unit Tests and Inso, the Insomnia CLI. Connect directly to Git providers to always be in sync with design changes and enable a GitOps pipeline with Inso, the Insomnia CLI tool. -
4
Jenkins
Build great things at any scale
Jenkins is the leading open-source automation server that allows you to build great things at any scale. Jenkins is built with Java and provides hundreds of plugins for building, deploying and automating virtually anything, allowing you to focus on more important things. Jenkins is often used for building projects, running tests, analyzing static code and deployment. Whatever is done repetitively, Jenkins can most likely execute and execute well, saving you time and optimizing your development process. Jenkins is easy to install, easy to configure and extensible via its plugin architecture. Start building smart with Jenkins! -
Save Up to 91% on Cloud Compute With Spot VMsRun batch jobs at 60-91% off with Spot VMs. Long-running workloads get automatic discounts with sustained use.
-
5
Argo CD
Declarative continuous deployment for Kubernetes
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Application definitions, configurations, and environments should be declarative and version controlled. Application deployment and lifecycle management should be automated, auditable, and easy to understand. Argo CD follows the GitOps pattern of using Git repositories as the source of truth for defining the desired application state. Argo CD automates the deployment of the desired application states in the specified target environments. Application deployments can track updates to branches, tags, or pinned to a specific version of manifests at a Git commit. See tracking strategies for additional details about the different tracking strategies available. Argo CD is implemented as a kubernetes controller which continuously monitors running applications and compares the current, live state against the desired target state (as specified in the Git repo). -
6
Keploy
Testing for Developers. Toolkit that creates test-cases and data mocks
Keploy is a functional testing toolkit for developers. It generates E2E tests for APIs (KTests) along with mocks or stubs(KMocks) by recording real API calls. KTests can be imported as mocks for consumers and vice-versa. Merge KTests with unit testing libraries(like Go-Test, JUnit..) to track combined test coverage. KMocks can also be referenced in existing tests or use anywhere (including any testing framework). KMocks can also be used as tests for the server. Keploy is added as a middleware to your application that captures and replays all network interaction served to the application from any source. Keploy has native interoperability as it integrates with popular testing libraries like go-test, junit. Code coverage will be reported with existing plus KTests. It'll also be integrated in CI pipelines/infrastructure automatically if you already have go-test, junit integrated. -
7
cypress
Fast, easy and reliable testing for anything that runs in a browser
The web has evolved. Finally, testing has too. Fast, easy and reliable testing for anything that runs in a browser. Installing Cypress is simple. No dependencies, extra downloads, or changes to your code required. Write tests easily and quickly, and watch them execute in real time as you build your web application. Debugging your tests in CI is as easy as running tests locally. With built in parallelization and load balancing. Record CI test results, screenshots and video, and view aggregated, next-level insights in your dashboard. Build up a suite of CI tests, record their results and gain powerful insights. Install the Cypress Test Runner and write tests locally. Cypress has been made specifically for developers and QA engineers, to help them get more done. Cypress is based on a completely new architecture. No more Selenium. Lots more power. -
8
CruiseControl.NET
An automated continuous integration server for the .NET platform
CruiseControl.NET is an automated continuous integration server for the .NET platform. It is a C# port of CruiseControl for Java. -
9
Buildbot
Python-based continuous integration testing framework
Buildbot is an open-source framework for automating software build, test, and release processes. At its core, Buildbot is a job scheduling system: it queues jobs, executes the jobs when the required resources are available, and reports the results. Your Buildbot installation has one or more masters and a collection of workers. The masters monitor source-code repositories for changes, coordinate the activities of the workers, and report results to users and developers. Workers run on a variety of operating systems. You configure Buildbot by providing a Python configuration script to the master. This script can be very simple, configuring built-in components, but the full expressive power of Python is available. This allows dynamic generation of configuration, customized components, and anything else you can devise. The framework itself is implemented in Twisted Python, and compatible with all major operating systems. -
Train ML Models With SQL You Already KnowBuild and deploy ML models using familiar SQL. Automate data prep with built-in Gemini. Query 1 TB and store 10 GB free monthly.
-
10
Atlas
A modern tool for managing database schemas
atlas is an open-source schema migration tool. Atlas is a tool for managing and migrating database schemas using modern DevOps principles. It offers two workflows. Similar to Terraform, Atlas compares the current state of the database with the desired state defined in an HCL or SQL schema, and generates a migration plan to reach that state. Unlike other tools, Atlas automatically plans schema migrations for you. Users can describe their desired database schema in HCL or SQL and use Atlas CLI to plan, lint, and apply the necessary migrations. The atlas schema command offers various options for inspecting, diffing, comparing, and modifying database schemas. The atlas migrate command provides a state-of-the-art experience for planning, linting, and applying migrations. Atlas integrates with standard cloud services and provides an easy way to read secrets from cloud providers such as AWS Secrets Manager and GCP Secret Manager. -
11
Concourse
Concourse is a container-based continuous thing-doer written in Go
Built on the simple mechanics of resources, tasks, and jobs, Concourse presents a general approach to automation that makes it great for CI/CD. Concourse is designed to be expressive, versatile, and safe, remaining intuitive as the complexity of your project grows. A Concourse pipeline is like a distributed, continuous Makefile. Each job has a build plan declaring the job's input resources and what to run with them when they change. Your pipeline is then visualized in the web UI, taking only one click to get from a failed job to seeing why it failed. The visualization provides a "gut check" feedback loop: if it looks wrong, it probably is wrong. Jobs can depend on other jobs by configuring passed constraints. The resulting chain of jobs and resources is a dependency graph that continuously pushes your project forward, from source code to production. -
12
Harness
Harness Open Source is an end-to-end developer platform
Harness is a CI/CD platform (available as SaaS/On-prem) that automates build, test, and deployment workflows. It offers pipeline-as-code YAML definitions, AI-optimized builds, policy-driven governance, multi-environment deployment templates (canary, blue/green), and integrated security scanning. -
13
Job DSL Plugin
Define Jenkins jobs using Groovy-based domain-specific language
The Job DSL Plugin allows Jenkins users to define and manage their jobs using a Groovy-based domain-specific language (DSL). This enables infrastructure-as-code for Jenkins jobs, making CI/CD pipelines reproducible, version-controlled, and easy to update. The plugin simplifies the creation of complex build configurations and supports templates, conditional logic, and job generation through scripts. -
14
Act
Run your GitHub Actions locally
When you run Act it reads in your GitHub Actions and determines the set of actions that need to be run. It uses the Docker API to either pull or build the necessary images, as defined in your workflow files, and finally determines the execution path based on the dependencies that were defined. Once it has the execution path, it then uses the Docker API to run containers for each action based on the images prepared earlier. The environment variables and filesystem are all configured to match what GitHub provides. -
15
Captain
Convert your Git workflow to Docker containers
Captain - Convert your Git workflow to Docker containers ready for Continuous Delivery. Define your workflow in the captain.yaml and use captain to your Continuous Delivery service to create containers for each commit, test them and push them to your registry only when tests passes. Use captain build to build your Dockerfile(s) of your repository. If your repository has local changes the containers will only be tagged as latest, otherwise the containers will be tagged as latest, COMMIT_ID & BRANCH_NAME. Now your Git commit tree is reproduced in your local docker repository. Use captain test to run your tests. Use captain push to send selected images to the remote repository. From the other side, you can now pull the feature branch you want to test, or create distribution channels (such as 'alpha', 'beta', 'stable') using git tags that are propagated to container tags. Captain will automatically configure itself with sane values without the need for any pre-configuration. -
16
Jenkins Docker
Docker jenkins repo
The Jenkins Continuous Integration and Delivery server available on Docker Hub. The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project. If you bind mount in a volume, you can simply back up that directory (which is jenkins_home) at any time. This is highly recommended. Treat the jenkins_home directory as you would a database, in Docker you would generally put a database on a volume. If your volume is inside a container, you can use a Docker command to extract the data, or other options to find where the volume data is. Note that some symlinks on some OSes may be converted to copies (this can confuse jenkins with lastStableBuild links etc). You can define the number of executors on the Jenkins built-in node using a groovy script. By default it is set to 2 executors, but you can extend the image and change it to your desired number of executors. -
17
Jenkins X CLI
Jenkins X provides automated CI+CD for Kubernetes
Jenkins X provides automated CI+CD for Kubernetes with Preview Environments on pull requests using cloud-native pipelines from Tekton. Automate the continuous delivery of change through your environments via GitOps and create previews on pull requests to help you accelerate. Each team gets a set of Environments. Jenkins X then automates the management of the Environments and the Promotion of new versions of Applications between Environments via GitOps and pull requests. Jenkins X automatically spins up Preview Environments for your pull requests so you can get fast feedback before changes are merged to the main branch. Jenkins X automatically comments on your Commits, Issues and pull requests with feedback as code is ready to be previewed, is promoted to environments or if pull requests are generated automatically to upgrade versions. -
18
OpsManage
Automated operation and maintenance platform
Automated operation and maintenance platform: code and application deployment CI/CD, asset management CMDB, scheduled task management platform, SQL audit | rollback, task scheduling, on-site WIKI. A code deployment, application deployment, scheduled tasks, and equipment asset management platform. Welcome to star or fork my open source project. If you need to quote the project code in your own project, please declare the agreement and copyright information in the project. Programming language, Python3.6 + HTML + JScripts. Front-end web framework, Bootstrap. Backend Web Framework, Django. Backend Task Framework, Celery + Redis. Programming language is Python 3.6. Operating System is CentOS 6+. Ansible version 2.6+. Deployment platform and node server Rsync 3+. -
19
Screwdriver API
An open source build platform designed for continuous delivery
Screwdriver is an open-source build platform designed for Continuous Delivery. Screwdriver began as a hack for simplified interfacing with Jenkins at Yahoo in 2012. As the volume of builds increased, it became clear that Jenkins was not stable or feasible to use at the scale we were running builds. In 2016, we rebuilt Screwdriver from scratch in open source with our best coding practices and CICD goals in mind. Screwdriver is executor and SCM-agnostic, meaning you can choose whichever plugin better suits your need or build your own. It's completely free and open-source, and our team is actively maintaining the code. Screwdriver is a self-contained, pluggable service to help you build, test, and continuously deliver software using the latest containerization technologies. We support an expanding list of source code services, execution engines, and databases so Screwdriver can work in your ecosystem. -
20
bors-ng
A merge bot for GitHub Pull Requests
bors-ng is a GitHub merge bot that enforces an “evergreen” main branch by queueing approved pull requests, testing them together on a staging branch, and only advancing main with the exact, passing commit set. Instead of maintainers repeatedly rebasing and merging one PR at a time, bors-ng batches r+-ed PRs, triggers your existing CI (e.g., GitHub Actions), and merges automatically when the batch is green. If a batch fails, it bisects the batch into smaller runs to isolate the culprit, landing the good PRs and kicking only the failing one(s) back for fixes. The bot is implemented as a GitHub App and works alongside—rather than replacing—your CI by reporting commit statuses/checks and acting on PR comments like bors r+ or bors try. It provides a dashboard to watch queue progress, uses separate staging/trying branches for merge/test cycles, and supports both public GitHub and GitHub Enterprise endpoints. -
21
werf
The CLI tool gluing Git, Docker, Helm, and Kubernetes
werf is an Open Source CLI tool written in Go, designed to simplify and speed up the delivery of applications. To use it, you need to describe the configuration of your application (in other words, how to build and deploy it to Kubernetes) and store it in a Git repo, the latter acts as a single source of truth. In short, that's what we call GitOps today. werf is not a complete CI/CD solution, but a tool for creating pipelines that can be embedded into any existing CI/CD system. It literally "connects the dots" to bring these practices into your application. We consider it a new generation of high-level CI/CD tools. werf builds Docker images using Dockerfiles or an alternative fast built-in builder based on the custom syntax. It also deletes unused images from the Docker registry. werf deploys your application to Kubernetes using a chart in the Helm-compatible format with handy customizations and improved rollout tracking mechanism, error detection, and log output. -
22
Displays the status of continuous integration servers in the Mac OS X menu bar. Works with all servers that support "cctray" feeds, which includes ThoughtWorks Go, Jenkins, Travis, and others.
-
23
Continuous Integration for .NET: Draco.NET is a Windows service application designed to facilitate continuous integration.
-
24
dbglider-devops
Database Change Promotion and Release Management Software
A complete database devops solution. It defines continuous integration and continuous deployment process for database application. It makes database application development and release management just like any other code application CI/CD. The software is provided with an easy user friendly UI interface to define the CI/CD for complex database application. Creation of new project, baseline, CI/CD, access management and many other functionalities offer through easy to understand screens. The current version of the software which consists of complete DevOps solution for database application is absolutely FREE. It offers unlimited downloads, unlimited users and FREE upgrades to all the future enhancements and bug fixing. For complete details, please visit to www.dbglider.com -
25
JCCTray is a utility for use with all flavors of CruiseControl Continuous Integration servers. It provides feedback upon build progress, and allows control over some of the server's operations.
Open Source CI/CD Tools Guide
Open source CI/CD tools are software solutions that enable organizations to automate the processes of building, testing and deploying applications. They are designed to expedite the release of new products or services, allowing teams to move faster and improve their time-to-market agility. Commonly used in DevOps environments, open source CI/CD tools can help reduce manual errors and streamline the build, test and deployment process for development teams.
These open source automated environment management tools allow for continuous integration (CI), which automates the process of merging code branches back into a main branch through various stages such as unit tests, static code analysis and version control. Continuous delivery (CD) is an automated deployment workflow that eliminates manual steps in the deployment process. This allows developers to focus on developing features instead of managing deployments. As part of CD, automated testing ensures all changes don’t break existing features or introduce bugs into a production environment.
Examples of popular open source CI/CD tools include Jenkins, GitLab CI/CD, TravisCI and CircleCI. Each platform offers different advantages when it comes to configuring pipelines or delivering fast results with minimal effort from a team’s perspective; however they all share some common characteristics such as cloud management capabilities for managing resources (e.g., Infrastructure as Code) via scripting languages (such as Ruby). In addition, platforms typically have APIs that allow users to integrate with other systems like databases or external webhooks for more advanced automation scenarios such as triggering builds based on certain events from third party services. Finally these types of open source platforms may also provide additional security benefits by leveraging technologies like containerization which ensure applications are securely sandboxed away from any potential attack vectors outside your network infrastructure enabling teams to confidently build & deploy without worrying about data breaches etc
Features Offered by Open Source CI/CD Tools
- Automated Testing: Open source CI/CD tools provide automated testing of code to ensure it meets requirements and does not contain bugs or flaws. This allows developers to ensure their code is working properly before putting it into production.
- Code Sharing: CI/CD tools come with version control systems like Git, which allow coders to share their work with colleagues so they can collaborate on projects together.
- Continuous Integration: This feature allows developers to continuously integrate new changes in the development process by monitoring repository commits closely. This helps make sure that any potential issues are caught right away, reducing the chances of serious problems occurring later on.
- Source Control Management: Tools such as Jenkins provide options for managing project repositories, making it easier to track changes made over time and quickly rollback if necessary.
- Automated Deployment: Open source CI/CD tools support automated deployments so teams can quickly and reliably deploy applications without manual intervention or risk of human error causing problems later down the line.
- Reporting & Metrics Tracking: Most open source CI/CD tools offer some kind of reporting tool that tracks metrics such as test runs, build status, etc., allowing teams to easily monitor performance and pinpoint areas needing improvement.
Different Types of Open Source CI/CD Tools
- Jenkins: Jenkins is an open-source automation server that helps configure, test, and deploy various applications. It typically offers a wide range of plugins and integrations to help automate the software development cycle.
- GitLab CI/CD: GitLab CI/CD is a fully featured continuous integration/delivery suite built into GitLab. It allows users to easily set up pipelines for building, testing, improving, deploying and monitoring their applications.
- Travis CI: Travis CI is a popular cloud-based continuous integration service that works with Github projects. It enables developers to easily set up automated builds and tests which can be triggered on every commit or pull request they make to their projects including the running static analysis tools such as linters and code coverage calculators.
- CircleCI: CircleCI is a powerful cloud-based platform designed for continuous integration and deployment of modern web applications and services. It allows users to build, test, deploy their apps with ease using configuration files written in YAML format that get stored in their repository root directory alongside other source codes.
- Drone CI/CD: Drone is an open source Continuous Delivery (CD) system based on containers technology that lets you easily build pipelines for your projects from scratch or from predefined templates defined in .drone file extension located at the root of your project workspace repository folder structure hierarchy tree diagram like most other DevOps systems do too nowadays when it comes to configuring the entire environment setup from beginning till the end stages such as deploying your application onto customer's servers etc.
Advantages Provided by Open Source CI/CD Tools
- Cost savings: Open source CI/CD tools are free, allowing companies and organizations to save money on software licensing costs.
- Streamlined development process: Open source CI/CD tools help streamline the development process by automating the building, testing, and deployment of code. This helps teams be more efficient in their workflow.
- Customization: Because open source tools can be modified to fit a team’s needs, it allows for greater customization, leading to better user experience and improved productivity.
- Increased scalability: Open source CI/CD tools provide increased scalability that wouldn’t be available with traditional solutions, allowing larger projects or applications to scale quickly without additional cost or infrastructure requirements.
- Improved security: Open source solutions are typically maintained by a community of developers who are constantly testing and updating them with new features and bug fixes as they become available. This helps ensure any security related issues are dealt with promptly.
- Community support: Many open source projects have strong communities where members can offer support to one another in using the tool or troubleshooting any issues that arise. This is especially helpful for non-technical users who may not know how to navigate the platform on their own.
What Types of Users Use Open Source CI/CD Tools?
- DevOps Engineers: Responsible for developing and maintaining continuous delivery pipelines, devops engineers rely on open source CI/CD tools to quickly build and deploy software.
- Developers: Developers make use of CI/CD tools as part of their regular workflow, using them to automatically run tests, manage builds, and package up code.
- System Administrators: System administrators leverage open source CI/CD solutions to automate server provisioning and deployment processes in order to save time on manual tasks.
- Data Analysts: Data analysts are able to utilize open source CI/CD solutions for gathering metrics about deployments or for orchestrating data processing jobs.
- Quality Assurance Professionals: Quality assurance professionals use open ssource CI/CD solutions to streamline their process of running quality checks before code goes live in production environments.
- IT Security Analysts: IT security analysts continuously evaluate the security posture of applications by taking advantage of the automation capabilities offered by open source CI/CD solutions.
How Much Do Open Source CI/CD Tools Cost?
Open source CI/CD tools don't actually cost anything, as they are completely free and open to use. For those new to developing software, having access to these types of tools can be a huge help in streamlining their development processes. Open source CI/CD tools have become increasingly popular over the last few years due to their flexibility and cost savings when compared with other alternatives. These tools can be used for anything from build automation, testing and deployment all the way up to monitoring production environments. With open source tools, users do not need to worry about upgrade costs or ongoing licensing fees – instead, everything is free for anyone who wishes to benefit from its use. This makes it easier for individuals and small business who cannot afford expensive commercial solutions. It also facilitates collaboration between different developers working on complex projects as each user can work on various parts of the project without worrying about financial restrictions. In this sense, open source CI/CD tools provide a great way for developers of any size or skill level to quickly develop high quality software applications at no cost but with the same level of professional quality that more expensive paid options might offer.
What Software Can Integrate With Open Source CI/CD Tools?
Open source CI/CD tools are designed to integrate with a variety of software products. This includes development frameworks such as Java, Python, and Node.js; build tools such as Maven, Gradle, and Ant; version control systems such as Git and Subversion; deployment platforms like Kubernetes and Docker; testing frameworks such as JUnit and Selenium; monitoring solutions like Prometheus or New Relic; and cloud providers like Amazon Web Services (AWS) or Microsoft Azure. These integration points provide the ability to automate parts of the software delivery process, streamline communication between operational teams, capture artifacts from builds, store deployable versions of applications in centralized locations, run tests without manual intervention, track team progress on projects over time, access real-time analytics about system health during production releases, and more.
What Are the Trends Relating to Open Source CI/CD Tools?
- Increased Adoption: Open source CI/CD tools have seen an increase in adoption due to their free cost as well as their flexibility and scalability. This has led to a large number of organizations, both small and large, turning to open source tools for their CI/CD needs.
- Enhanced Automation: The use of open source CI/CD tools has enabled organizations to create sophisticated automated pipelines that can be used to quickly and efficiently deliver new applications and features. This automation has improved the development process by reducing the amount of manual work required for each release cycle.
- Improved Quality: Open source CI/CD tools have helped improve the quality of software releases by providing organizations with automated tests and analysis capabilities. This helps teams identify bugs earlier on in the development process, allowing them to be fixed before they reach production.
- Increased Security: Open source CI/CD tools provide organizations with enhanced security capabilities, allowing them to securely deploy applications and new features without compromising on quality or speed. This makes it easier for organizations to comply with security regulations and standards.
- Customization Possibilities: With open source CI/CD tools, teams are able to customize their pipelines according to their specific needs and requirements. This allows them to tailor their pipelines so that they can meet their business objectives while still ensuring high-quality releases.
How To Get Started With Open Source CI/CD Tools
- Familiarize yourself with the process: Before diving into any specific tool, it's important to understand how CI/CD works in theory and practice. This will help you make the most of your choice of open source CI/CD tools.
- Choose a tool: There are countless options available, from Jenkins to Drone.io, so take the time to research each one and find something that fits your project requirements.
- Configure settings: Once you've chosen a platform, configure all necessary settings such as version control, integration patterns, and alerts according to your particular software setup.
- Begin testing: After configuring settings, begin testing the platform using different builds or scripts depending on what type of application or software you’re working on. You can also set up simulations during this stage to ensure any new features won't cause unexpected issues in your live environment.
- Automate builds: Finally, automate build processes based on which continuous integration triggers best suit your needs. If possible try automating as much of the development workflow as possible so that less manual effort is required every time code changes occur throughout development cycle.
