Open-source AppVeyor alternatives

Gitea is a software development service written in Go that you host yourself and that brings the usual tooling together in one place. It combines Git hosting, code management and review, issue tracking, project kanban boards, a wiki, team collaboration, a package registry and CI/CD, with the aim of being the easiest and least painful way to run your own code platform. Its topics place it in the same space as GitHub and GitLab.

Because it is written in Go, Gitea runs on any platform Go supports: Linux, macOS, the BSDs and Windows, across x86, amd64, ARM, RISC-V 64 and PowerPC processors. Package registries such as Maven, npm and Docker are mentioned in its topics, and its CI/CD system can reuse GitHub Actions workflows, which eases migration of existing pipelines. Documentation covers installation, administration and development.

The project is MIT licensed. You can try a public demo at demo.gitea.com, use the free service at gitea.com with a limited number of repositories, start a trial of the managed Gitea Cloud, or deploy the official container image on your own server. It suits teams and individuals who want control over their source code hosting.

Harness Open Source is a developer platform written in Go that bundles source code hosting, automated pipelines, hosted development environments and artifact registries in one product. The idea is to give a team a complete, self-run DevOps toolchain rather than separate services for repositories, builds and package storage.

Its hosted development environments are called Gitspaces, and the platform also includes registries for build artifacts. Harness is presented as the next generation of Drone: Drone focused only on continuous integration, whereas Harness adds code hosting and developer environments. The maintainers say the goal is eventual parity with Drone's pipeline capabilities so users can migrate, and a snapshot of Drone lives on a separate branch so it can keep developing.

You can run Harness locally from the published Docker image and open it on port 3000. The image stores its database and repositories in a volume, so a bind mount or named volume is strongly recommended to avoid losing data when the container stops. The project is Apache-2.0 licensed, with documentation at developer.harness.io.

Jenkins is an open-source automation server written in Java. Teams use it to automate parts of their development workflow, including building projects, running tests to catch bugs early, performing static code analysis and deploying software. The README states that more than 2,000 plugins extend it to automate nearly any task. It is released under the MIT license, and its topics include continuous integration, delivery and pipelines as code.

The project distributes official downloads as WAR archives, Docker images, and native packages or installers for several Linux distributions and Windows. Two release lines exist: weekly releases carrying all new features and fixes, and Long-Term Support releases that receive periodic backported bug fixes. The repository links to contributing guidelines, good first issues, developer documentation, governance and adopters information. As a self-managed server, you operate and secure your own Jenkins instance.

GitLab is a platform for collaborating on code. This GitHub repository is a mirror of the Community Edition, written in Ruby on Rails, while the canonical source and all development take place on GitLab.com. Issues should be opened on the GitLab.com tracker rather than here. The platform manages Git repositories with fine-grained access controls, merge requests for code review, and per-project issue trackers, boards and wikis.

GitLab includes continuous integration and delivery pipelines to build, test and deploy applications. It follows an open-core model: most of the code is MIT-licensed, while files in the ee directory are proprietary but source-available. Three editions exist: Community Edition, free under the MIT Expat license; Enterprise Edition, with extra features aimed at organizations with more than 100 users and sold by subscription; and JiHu Edition for the Chinese market. A free trial of the Ultimate tier is available.

OneDev is a self-hosted platform that gathers Git hosting, issue tracking, pull requests, CI/CD, packages, a wiki and workspaces in one place. It is described as unified and autonomous, with AI teammates available to help with development work. The team develops OneDev on its own instance at code.onedev.io, where issues and pull requests are submitted.

The feature set emphasizes code review and quality. There is language-aware symbol search and navigation within any commit, fast code search with regular expressions, a Renovate integration that updates dependencies through pull requests which can merge automatically after approval or passing tests, and code annotated with coverage and problems found in the CI/CD pipeline. Discussions can be started on any code selection or diff and stay attached to the code, and versatile protection rules can require reviews or CI verification when particular users change particular files on particular branches. Topics also mention kanban boards.

OneDev is written in Java and licensed under MIT. You host it yourself, which suits teams wanting an all-in-one alternative to stitching together GitHub-like hosting, CI and project tools. Tutorials and demos on the project site show features such as dependency updates and protection rules in action.

Concourse is an automation system written in Go, most often used for CI/CD and built to scale from simple to complex pipelines. It is deliberately opinionated: the project emphasizes idempotency, immutability, declarative configuration, stateless workers and reproducible builds.

It is distributed as a single concourse binary on the releases page, and other supported formats include a Docker image, a Kubernetes Helm chart and a BOSH release. A quick start walks through running it locally. Topics show that tasks run in containers using containerd and runc, and the web interface was built with Elm.

Concourse is licensed under Apache-2.0. It is run on your own infrastructure by teams that prefer pipelines described as code, with each job's inputs and outputs explicit, over scripts configured through a UI. It suits platform and DevOps teams wanting repeatable, container-isolated build and deploy pipelines.

Woodpecker is a simple CI/CD engine with a plugin system for extending what pipelines can do. It can be installed in several ways, including Docker and Kubernetes, and runs with SQLite as the default database, so a small setup needs little more than a server and one or more agents.

The README says the server needs around 100 MB of memory and the agent about 30 MB when idle, which makes it suitable for modest hardware. Plugins are browsed on a dedicated overview website and include both core-team and community-maintained ones. Translations are managed on a self-hosted Weblate instance, and the project is supported through Open Collective and GitHub Sponsors.

Woodpecker is written in Go and licensed under Apache-2.0, with documentation under Creative Commons Attribution-ShareAlike. Codeberg, a Git hosting platform focused on privacy and free software, uses it as its main CI/CD engine. It suits teams and individuals who self-host Git and want a lean container-based pipeline runner.

GoCD is a continuous delivery server that helps automate and streamline the build, test and release cycle so that software can be delivered continuously with fewer worries. The repository is the project's main code base, and the project is sponsored by Thoughtworks.

Newcomers can use the Test Drive GoCD page to build a first pipeline while learning the key concepts, download releases from the website and read the documentation for detailed help. It is predominantly a Java and TypeScript project that uses the Spring Framework, SparkJava and MithrilJS, is built with Gradle and Webpack and runs inside Eclipse Jetty, with a few older parts rendered server-side in JRuby on Rails. GoCD itself is built with GoCD.

The security policy explains how issues are reported, and contributing guides cover the development environment. GoCD is licensed under Apache-2.0 and is hosted by you. It suits teams that model deployment pipelines with explicit stages and dependencies across several services.

Buildbot is an open-source continuous integration framework written in Python. Rather than a fixed service with a rigid workflow, it is a toolkit for automating the whole software development cycle, from compiling and testing code to packaging and releasing it, with configuration expressed in Python.

The project's site presents it as a framework with batteries included, covering automated build, test and release jobs, a web interface, and a tutorial and documentation to get started. A master process coordinates build workers that can run on different platforms, which makes it a good fit for projects that need to test across many operating systems and configurations. The site also lists success stories and a Metabuildbot used to build Buildbot itself.

Buildbot is licensed under GPL-2.0 and is typically self-hosted, with community support through a mailing list and IRC. It suits teams that want a highly customizable CI system they control, particularly for complex or multi-platform build setups.

Semaphore is a continuous integration and delivery platform that helps product teams build, test and ship software. Pipelines are defined in YAML, can run jobs in parallel, and work with containers, Kubernetes and multi-cloud environments. The project presents it as a delivery platform for AI-driven development as well as traditional workflows.

The code base is written mainly in Elixir and Go, and the repository describes three flavors. The Community Edition is free and open source under Apache 2.0 and meant for teams running Semaphore on their own infrastructure with community support. The Enterprise Edition adds features for larger organizations under a commercial licence with professional support. Semaphore Cloud is the hosted option at semaphoreci.com.

Installing the self-hosted version is said to take roughly 10 to 30 minutes, with detailed guides for different methods, and the repository links to documentation, a roadmap, governance information and a project board. It suits engineering teams that want a modern CI/CD system they can run themselves, or prefer a hosted service with the same engine.