My Very Own CI-server
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Stefan Naumann 7a2387665a replace ' ' by '_' in filenames 2 weeks ago
build replace ' ' by '_' in filenames 2 weeks ago
core Removed State secret, just use public repos for that 1 month ago
hook core/log: modified logger to use golangs log not fmt 7 months ago
static added build-finished and failed-images for stuff like github 1 month ago
views repo-view: +Advanced Build in Javascript 1 month ago
web fixed repo-state bug; minor changes 3 weeks ago
.gitignore Installer: fixed bugs in postgreSQL database server support 7 months ago
LICENSE Initial commit 11 months ago
Makefile made zip downloads save 1 month ago „“ ändern 1 month ago
main.go rewritten config to use JSON files, listing of login tokens on User-edit page, white logo variant 5 months ago
mvo.cfg added build-finished and failed-images for stuff like github 1 month ago


My Very Own CI-server (Continuous Integration). With it you can build Git-repositories with webhooks, i.e. whenever commits are pushed or on the press of a button.

mvoCI aims to be simple and do as much as is necessary and nothing more. No Plugins, no Modules, no 500 MB of RAM eaten (your mileage may vary).

Be advised, that mvoCI has shell access. It is your responisibility to secure your machine from damage by mvoCI.

What it does

  • organize Repositories and Builds of them
  • build Repositories on webhook, on click “Build Now”
  • have a rudimentary account management
  • bindings to Gogs, Gitea, Gitbucket, and Github

What it does not

  • Anything more, like
    • timed builds
    • after build scripts
    • SVN, Mercurial, VCS (although there should not be a real reason for this constraint)
    • internationalization (currently only English)


Build-time Dependencies

mvoCI uses the following golang libraries:


Install with:

go get


You need a database server, or use SQLite as database backend. You may use one of the following:

  • PostgreSQL
  • MySQL / MariaDB
  • SQLite3

Set up

  • ./mvo --install for the installation dialogues
  • ./mvo for production mode


  • Configuration options are in mvo.cfg.


LogFile              -> path to the log file
LogFileEnable        -> (bool) should a log-file be produced?
LogMode              -> write logs also to the terminal on (stderr/stdout)
app_title            -> Name your Instance
compression_method   -> compression method used for archiving build artifacts (e.g. gz)
database_provider    -> what database backend do you use?
    -> based on that more database-options, the Install dialog helps you configuring these
debug                -> (bool) more verbose output
dir_build            -> path to where the build artifacts are stored
dir_repo             -> path to where the repos are cloned to on build
host                 -> hostname of the server
http_port            -> (int) port, the server listens to
impress_*            -> information about the administrator for impress (city, mail, owner, street, zip)
impress_privacy      -> privacy statement
login_token_duration -> (int) specifies how long the login-token stays valid (in seconds)
parallel_builds      -> (int) the number of build threads and therefore the number of possible builds in parallel on the instance

Lock down

As stated earlier, it is recommended, that mvoCI is not executed as root. It should be used with as little rights are possible, but enough to be useful for your usecase.


You may use this script to start mvoCI automatically as an own user (e.g. mvo). Please make sure, that that user cannot do anything you wouldn't do yourself!


Environment=USER=mvo HOME=/home/mvo