Laminar alternatives and similar tools
Based on the "Continuous" category.
Alternatively, view Laminar alternatives based on common mentions on social networks and blogs.
Drone9.5 6.3 Laminar VS DroneDrone is a Container-Native, Continuous Delivery Platform
Go7.9 9.9 L4 Laminar VS GoMain repository for GoCD - Continuous Delivery server
Buildbot7.8 9.8 L3 Laminar VS BuildbotPython-based continuous integration testing framework; your pull requests are more than welcome!
concourse7.8 9.4 Laminar VS concourseConcourse is a container-based continuous thing-doer written in Go.
Strider7.2 0.0 L5 Laminar VS StriderOpen Source Continuous Integration & Deployment Server
CDS6.9 8.6 Laminar VS CDSEnterprise-Grade Continuous Delivery & DevOps Automation Open Source Platform
GitLab CI6.0 0.0 Laminar VS GitLab CIBased off of ruby. They also provide GitLab, which manages git repositories.
Jenkins5.7 9.8 Laminar VS JenkinsA static site for the Jenkins automation server
PHP Censor4.6 8.2 L4 Laminar VS PHP CensorPHP Censor is an open source self-hosted continuous integration server for PHP projects.
Factor2.5 0.0 L5 Laminar VS FactorFactor Server runs your continuous deployment workflows
GolangCI2.3 0.0 Laminar VS GolangCICentral issue tracker for the GolangCI project
CapsuleCD2.3 1.2 Laminar VS CapsuleCDContinuous Delivery for automating package releases (npm, cookbooks, gems, pip, jars, etc)
PHPCIFree and open source continuous integration specifically designed for PHP. (Source Code) BSD-2-Clause PHP
Access the most powerful time series database as a service
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Laminar or a related project?
Laminar (https://laminar.ohwg.net) is a lightweight and modular Continuous Integration service for Linux. It is self-hosted and developer-friendly, eschewing a configuration UI in favour of simple version-controllable configuration files and scripts.
Laminar encourages the use of existing GNU/Linux tools such as
cron instead of reinventing them.
Although the status and progress front-end is very user-friendly, administering a Laminar instance requires writing shell scripts and manually editing configuration files. That being said, there is nothing esoteric here and the guide should be straightforward for anyone with even very basic Linux server administration experience.
See the website and the documentation for more information.
Building from source
First install development packages for
capnproto (version 0.7.0 or newer),
boost (for the header-only
multi_index_container library) from your distribution's repository or other source.
On Debian Buster, this can be done with:
sudo apt install \ capnproto cmake g++ libboost-dev libcapnp-dev libsqlite-dev libsqlite3-dev make rapidjson-dev zlib1g-dev
Then compile and install laminar with:
git clone https://github.com/ohwgiles/laminar.git cd laminar cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr make -j4 # Warning: the following will overwrite an existing /etc/laminar.conf sudo make install
make install includes a systemd unit file. If you intend to use it, consider creating a new user
laminar or modifying the user specified in the unit file.
Packaging for distributions
pkg directory contains shell scripts which use docker to build native packages (deb,rpm) for common Linux distributions. Note that these are very simple packages which may not completely conform to the distribution's packaging guidelines, however they may serve as a starting point for creating an official package, or may be useful if the official package lags.
Issues and pull requests via GitHub are most welcome. All pull requests must adhere to the Developer Certificate of Origin.