Open Source Linux CI/CD Tools - Page 2
Sort By:
CI/CD Tools for Linux
View 32 business solutions-
Full-stack observability with actually useful AI | Grafana CloudBuilt on open standards like Prometheus and OpenTelemetry, Grafana Cloud includes Kubernetes Monitoring, Application Observability, Incident Response, plus the AI-powered Grafana Assistant. Get started with our generous free tier today.
-
Go From AI Idea to AI App FastAccess Gemini 3 and 200+ models. Build chatbots, agents, or custom models with built-in monitoring and scaling.
-
1
-
2
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. -
3
The C'it (Continuous Integration and Testing) project (say "see it!") is a set of services to increase the perception of the evolving software, letting you easily implement continuous integration at its best.
-
4
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. -
AI-generated apps that pass security reviewRetool lets you generate dashboards, admin panels, and workflows directly on your data. Type something like “Build me a revenue dashboard on my Stripe data” and get a working app with security, permissions, and compliance built in from day one. Whether on our cloud or self-hosted, create the internal software your team needs without compromising enterprise standards or control.
-
5
Continuous Integration Demo - 4
An example project to demonstrate continuous integration, in HTML5..
Demonstration of a web based GUI using HTML, CSS, and Javascript. This project builds on the Continuous Integration Demo - Java - 2 and / or Continuous Integration Demo - Java - 3 projects. -
6
Continuous Integration Demo - Java
An example project to demonstrate continuous integration, in Java.
A simple example project demonstrating automated build and testing. This project is in Java, uses Ant for the build script, and makes use of JUnit for unit testing. -
7
Continuous Integration Demo - Java - 2
An example project to demonstrate continuous integration, in Java.
Demonstrations of web services. This project builds on Continuous Integration Demo - Java. -
8
Continuous Integration Demo - Java - 3
An example project to demonstrate continuous integration, in Java.
Demonstrations of SOAP web services. This project builds on Continuous Integration Demo - Java. -
9
A Java Swing based library that allows a user to monitor multiple continuous integration server instances (Such as Hudson and CruiseControl instances) easily and effectively.
-
Enterprise-grade ITSM, for every businessFreshservice is an intuitive, AI-powered platform that helps IT, operations, and business teams deliver exceptional service without the usual complexity. Automate repetitive tasks, resolve issues faster, and provide seamless support across the organization. From managing incidents and assets to driving smarter decisions, Freshservice makes it easy to stay efficient and scale with confidence.
-
10
Continuous Integration Engine which allows concurrent building of dependent projects via ant scripts.
-
11
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. -
12
Dashboard is a plugin for IntelliJ IDEA and Eclipse that provides immediate visual feedback of the status of a (remote) continuous integration build process directly in the editor. It initially works with Cruise Control (or vanilla Ant).
-
13
Deepchecks
Test Suites for validating ML models & data
Deepchecks is the leading tool for testing and for validating your machine learning models and data, and it enables doing so with minimal effort. Deepchecks accompany you through various validation and testing needs such as verifying your data’s integrity, inspecting its distributions, validating data splits, evaluating your model and comparing between different models. While you’re in the research phase, and want to validate your data, find potential methodological problems, and/or validate your model and evaluate it. To run a specific single check, all you need to do is import it and then to run it with the required (check-dependent) input parameters. More details about the existing checks and the parameters they can receive can be found in our API Reference. An ordered collection of checks, that can have conditions added to them. The Suite enables displaying a concluding report for all of the Checks that ran. -
14
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. -
15
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. -
16
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. -
17
Growth In Action
Full stack growth engineer in action
What we introduce in Growth is just a series of practices, and the actual combat of Growth will lead readers to implement these practices. You will see how to develop a web application (blog). How to write tests - unit tests, functional tests, automated UI tests. Build and use continuous integration. Added SEO support - Sitemap, Webmaster Tools and Google Analytics. Create API, make AutoComplete. Develop the corresponding APP and its API - view articles, user login, publish articles. Make a Single Page Application. Configurable management. -
18
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.
-
19
JCruiseMonitor monitors the state of builds on your team's continuous integration server (Hudson, CruiseControl/.NET/.rb, Continuum or Bamboo), providing feedback through a set of devices including a tray icon, USB light and audible warnings.
-
20
The Java Integrated Build Environment is a build environment that combines XP concepts like Continuous Integration with existing tools like Ant, JUnit, CruiseControl, CVS and Tomcat, to provide the community with a tool to build, test and release software
-
21
Jenkins Remote is a system tray application that provides a detailed view of your Jenkins Continuous Integration server. It is design to sit in your operating system’s System Tray and query the Jenkins server for information about each job.
-
22
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. -
23
Jest Puppeteer
Run your tests using Jest & Puppeteer
Most continuous integration platforms limit the number of threads one can use. If you have more than one test suite running puppeteer chances are that your test will timeout. This is because jest will try to run puppeteer in parallel and the CI platform won't be able to handle all the parallel jobs in time. A fix to this is to run your test serially when in a CI environment. Users have discovered that running test serially in such environments can render up to 50% of performance gains. Writing integration test can be done using Puppeteer API but it can be complicated and hard because API is not designed for testing. Debugging tests can be hard sometimes and it is very useful to be able to pause tests in order to inspect the browser. Jest Puppeteer exposes a method jestPuppeteer.debug() that suspends test execution and gives you the opportunity to see what's going on in the browser. -
24
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. -
25
Kubespray
Deploy a Production Ready Kubernetes Cluster
Can be deployed on AWS, GCE, Azure, OpenStack, vSphere, Equinix Metal (bare metal), Oracle Cloud Infrastructure (Experimental), or Baremetal. Highly available cluster. Composable (Choice of the network plugin for instance). Supports most popular Linux distributions. Continuous integration tests. The list of available docker versions is 18.09, 19.03, and 20.10. The recommended docker version is 20.10. The kubelet might break on docker's non-standard version numbering (it no longer uses semantic versioning). To ensure auto-updates don't break your cluster look into e.g. yum version lock plugin or apt pin). The target servers must have access to the Internet in order to pull docker images. Otherwise, additional configuration is required. The target servers are configured to allow IPv4 forwarding. If using IPv6 for pods and services, the target servers are configured to allow IPv6 forwarding.
