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 414cda112f added vet target to Makefile 6 months ago
build build-script find function; oauth creds of the Repository owning users are used 6 months ago
core build-script find function; oauth creds of the Repository owning users are used 6 months ago
hook build-script find function; oauth creds of the Repository owning users are used 6 months ago
static oauth token views and key-exchange with gitea, gitea: push release builds to gitea, using oauth, separate build-script for releases 6 months ago
views queue on dashboard, fixed build-now using a wrong build script 6 months ago
web build-script find function; oauth creds of the Repository owning users are used 6 months ago
.gitignore Installer: fixed bugs in postgreSQL database server support 1 year ago
LICENSE Initial commit 1 year ago
Makefile added vet target to Makefile 6 months ago changed url in the footer, Readme lists gitlab and bitbucket 7 months ago
main.go rewritten config to use JSON files, listing of login tokens on User-edit page, white logo variant 1 year ago


Build Status

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 responsibility 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, Gitlab, Bitbucket 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