Open Source Go CI/CD Tools
Sort By:
Go CI/CD Tools
View 113 business solutionsBrowse free open source Go CI/CD Tools and projects below. Use the toggles on the left to filter open source Go CI/CD Tools by OS, license, language, programming language, and project status.
-
MongoDB Atlas runs apps anywhereMongoDB Atlas gives you the freedom to build and run modern applications anywhere—across AWS, Azure, and Google Cloud. With global availability in over 115 regions, Atlas lets you deploy close to your users, meet compliance needs, and scale with confidence across any geography.
-
Add Two Lines of Code. Get Full APM.Works out of the box for Rails, Django, Express, Phoenix, and more. Monitoring exceptions and performance in no time.
-
1
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). -
2
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. -
3
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. -
4
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. -
Custom VMs From 1 to 96 vCPUs With 99.95% UptimeLive migration and automatic failover keep workloads online through maintenance. One free e2-micro VM every month.
-
5
Flux
Open and extensible continuous delivery solution for Kubernetes
Flux is a tool for keeping Kubernetes clusters in sync with sources of configuration (like Git repositories and OCI artifacts), and automating updates to the configuration when there is new code to deploy. Flux version 2 ("v2") is built from the ground up to use Kubernetes' API extension system, and to integrate with Prometheus and other core components of the Kubernetes ecosystem. In version 2, Flux supports multi-tenancy and support for syncing an arbitrary number of Git repositories, among other long-requested features. Flux v2 is constructed with the GitOps Toolkit, a set of composable APIs and specialized tools for building Continuous Delivery on top of Kubernetes. Flux is a Cloud Native Computing Foundation (CNCF) project, used in production by various organisations and cloud providers. -
6
Gitness
Gitness is an Open Source developer platform with Source Control
Gitness is an open source development platform packed with the power of code hosting and automated DevOps pipelines. Gitness represents a massive investment in the next generation of drones. Where Drone focuses on continuous integration, Gitness adds source code hosting, bringing code management and pipelines closer together. The goal is for Gitness to eventually be at full parity with Drone in terms of pipeline capabilities, allowing users to seamlessly migrate from Drone to Gitness. -
7
Kargo
Application lifecycle orchestration
Kargo is a next-generation continuous delivery and application lifecycle orchestration platform for Kubernetes. It builds upon GitOps principles and integrates with existing technologies, like Argo CD, to streamline and automate the progressive rollout of changes across the many stages of an application's lifecycle. Kargo's goal is to provide an intuitive and flexible layer "above" existing GitOps tooling, wherein you can describe the relationships between various application instances deployed to different environments as well as procedures for progressing changes from one application instance's source of truth to the next. -
8
-
9
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. -
Our Free Plans just got better! | Auth0You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
-
10
Agola
Agola CI/CD Redefined
Execute your runs in a reproducible containerized environment. Restart them from start or from the failed tasks. Implement every kind of workflow you want from simple builds to complex deployments. GitHub, GitLab, Gitea, custom Git repositories (and more to come). Execute your tasks inside a Kubernetes cluster, local docker, etc. Keep the same Runs definition but use different variables values based on rules to test your runs on multiple environments. Runs definitions are committed inside your git repositories and triggered upon push/tag/pull request. Scalable and High Available: go from a single instance (single process) deployment to a distributed deployment. Deploy anywhere: Kubernetes, IaaS, bare metal and execute the "tasks" anywhere (currently containers executors like docker or orchestrators and Kubernetes, but easily extensible to future technologies or VMs instead of containers). Support any language, deployment system etc. (just use the right image). -
11
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. -
12
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. -
13
Cyclone
Powerful workflow engine and end-to-end pipeline solutions
Cyclone is a powerful workflow engine and end-to-end pipeline solution implemented with native Kubernetes resources, with no extra dependencies. It can run anywhere Kubernetes is deployed: public cloud, on-prem or hybrid cloud. Cyclone is architectured with a low-level workflow engine that is application agnostic, offering capabilities like workflow DAG scheduling, resource lifecycle management and most importantly, a pluggable and extensible framework for extending the core APIs. Above which, Cyclone provides built-in support for high-level functionalities, with CI/CD pipelines and AI DevOps being two notable examples, and it is possible to expand to more use cases as well. With Cyclone, users end up with the flexibility of workflow orchestration and the usability of complete CI/CD and AI DevOps solutions. Parameterization: stage (unit of execution) can be parameterized to maximize configuration reuse. -
14
Devtron
Tool integration platform for Kubernetes
Devtron deeply integrates with products across the lifecycle of microservices,i.e., CI, CD, security, cost, debugging, and observability via an intuitive web interface. Devtron is designed to be modular, and its functionality can be easily extended with the help of integrations. Devtron CI/CD with GitOps integration is used to automate the builds and deployments and enables the software development teams to focus on meeting the business requirements, code quality, and security. Devtron leverages Kubernetes auto-scaling and centralized caching to give you unlimited cost-efficient CI workers. Supports pre-CI and post-CI integrations for code quality monitoring. Provides deployment metrics like; deployment frequency, lead time, change failure rate, and mean-time recovery. Seamlessly integrates with Grafana for continuous application metrics like CPU and memory usage, status code, throughput, and latency on the dashboard. -
15
Drone
Drone is a Container-Native, Continuous Delivery Platform
Drone is a self-service Continuous Integration platform for busy development teams. Pipelines are configured with a simple, easy‑to‑read file that you commit to your git repository. Each Pipeline step is executed inside an isolated Docker container that is automatically downloaded at runtime. Drone integrates seamlessly with multiple source code management systems, including GitHub, GitHubEnterprise, Bitbucket, and GitLab. Drone natively supports multiple operating systems and architectures, including Linux x64, ARM, ARM64, and Windows x64. Drone works with any language, database, or service that runs inside a Docker container. Choose from thousands of public Docker images or provide your own. Drone uses containers to drop pre‑configured steps into your pipeline. Choose from hundreds of existing plugins, or create your own. Drone makes advanced customization easy. Implement custom access controls, approval workflows, secret management, yaml syntax extensions, and more. -
16
EARTHLY
The effortless CI/CD framework that runs anywhere
Share compute and cache with Earthly Satellites. Build remotely from the comfort of your terminal. Satellites use the code in your current directory, stream logs back to you in real time, and output results (images, artifacts) back to your laptop. When used from a CI, Earthly Satellites can be used to speed up builds, as the cache is retained between runs. Earthly was engineered for readability. Most engineers are able to read an Earthfile without any prior knowledge. We took some of the best ideas from Dockerfiles and Makefiles and combined them into one specification. Earthly builds are self-contained, isolated and repeatable. Regardless of whether Earthly runs in your CI or on your laptop, the build will run the same way. This allows for faster iteration and easier debugging. Unlock your team's full productivity by eliminating "works on my machine but not in CI" blockers. -
17
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. -
18
Infracost
Cloud cost estimates for Terraform in pull requests
Infracost scans for Terraform code changes and checks over 3 million prices to create a simple, understandable cost estimate before any resources are launched. Infracost integrates into CI/CD so everyone knows the cost impact of changes without leaving the workflow. Infracost integrates with Open Policy Agent, Sentinel, and Conftest, enabling DevOps teams to set best practices as policies. Infracost automatically creates detailed, shareable cost estimates which can be sent to clients and managers with different scenarios. Infracost supports over 230 Terraform resources across AWS, Azure and Google. Other IaC tools, such as Pulumi, AWS CloudFormation/CDK and Azure ARM/Bicep are on our roadmap. Infracost can also estimate usage-based resources such as AWS S3 or Lambda! Infracost has many CI/CD integrations so you can easily post cost estimates in pull requests. This provides your team with a safety net as people can discuss costs as part of the workflow. -
19
Pipeline Examples
A collection of examples, tips and tricks and snippets of scripting
This repository collects a variety of example Jenkins Pipeline scripts, tips, snippets, and patterns for both the declarative and scripted pipeline syntaxes. It includes examples for global shared libraries, Jenkinsfile variations, and usage of plugins, to help users adopt pipelines in their Jenkins automation workflows. Examples of plugin integrations (e.g. artifact upload, workspace management). Tips & tricks for script construction and structure. Pipeline patterns and best practices. -
20
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.
- Previous
- You're on page 1
- Next
