Jenkins

Hudson was an automation and continuous-integration project created in 2004 by Sun Microsystems engineer Kohsuke Kawaguchi to automate software build tasks. It later became Jenkins after Oracle claimed the Hudson trademark.

Openship is an open-source, self-hostable application deployment platform with built-in CI/CD. It takes a repository, detects or supports its stack, builds and ships the application as containers, and handles routing and TLS termination. Deployments can be controlled through a desktop app, web dashboard, or CLI; GitHub webhooks support push-to-deploy workflows, and the platform supports repeatable rollbacks. The control plane can run locally in the desktop app, as a self-hosted server, or through Openship Cloud. In Compose mode it runs the platform stack on a Docker host and can host deployed applications there; in bare mode it runs as a lightweight process and deploys to a server over SSH or to the cloud.

A CI/CD and automation platform from GitHub (Microsoft) that runs YAML-defined workflows in response to repository events, schedules, or API calls. Workflows orchestrate jobs on GitHub-hosted or self-hosted runners (Ubuntu, Windows, macOS or custom runners), invoke container, JavaScript or composite actions, and produce artifacts (build outputs, test reports, generated files). It supports secrets, caching, matrix and reusable workflows, the Actions Marketplace, and can run arbitrary CLI tools (for example, invoking a D2 CLI in a workflow to generate architecture diagrams from D2 source files).

Heroku is a managed cloud application platform for deploying, running, and scaling software without manually managing servers, operating systems, runtimes, web servers, or deployment scripts. Its deployment workflow uses Git push commands and buildpacks to turn application code into runnable deployments on container-based infrastructure, following the Twelve-Factor App principles.

Tekton Pipelines is an open-source, Kubernetes-native system for declaring and running CI/CD-style pipelines through Kubernetes-style resources. Pipelines are composed of Tasks, which can run independently; they use containers as building blocks, treat Kubernetes clusters as a first-class target, and support swappable typed resources such as image-building implementations. The project is designed for self-managed CI and workflow environments and can use one Pipeline to deploy to different Kubernetes clusters.