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.
Jens Zahner d8daaaec1f Improve Advanced Build function (#40) 5 months ago
auth docs: auth and build documentation, link to docs 1 year ago
build build.js: added support for liveLog to JavaScript API calls 8 months ago
core Integrated sub-url support into mvoCI. 7 months ago
hook docs: hook and started web 1 year ago
static Improve Advanced Build function (#40) 5 months ago
views Improve Advanced Build function (#40) 5 months ago
web Improve Advanced Build function (#40) 5 months ago
.gitignore Installer: fixed bugs in postgreSQL database server support 3 years ago
LICENSE Initial commit 4 years ago
Makefile changed imports to use the new codeberg name 1 year ago deprecation notice on release build script 8 months ago
go.mod updated dependencies 8 months ago
go.sum updated dependencies 8 months ago
main.go create default config with cli-argument for easier installation behind sub-url'd proxy 7 months ago


Build Status Go Docs

My Very Own CI-server (Continuous Integration), a personal continuous integration system. mvoCI builds code from git repositories either on user-input, via an API call or on webhooks, i.e. whenever someone pushed commits to the git or when new releases are added.

mvoCI aims to be simple and do as much as is necessary and nothing more. It aims to have a small memory footprint, be easy to use and understand.

It is intended as a personal continuous integration server, useful for your private builds or builds of a team, who know and trust each other. It is not intended to be used for the public, for untrusted repositories or with untrusted co-users.

Be advised, that mvoCI uses shell access for its building routines. It is your responsibility to secure your machine from damage or data leakage by mvoCI.

What it does

  • organize Repositories and Builds of them
  • build Repositories on webhook or on click "Build Now"
  • build and publish release-artifacts to Gitea automatically
  • 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 (only English)

Deprecation Notices

  • Going forward the division between Release and Push Build script will be removed and only the push build script will be kept going forward. Make sure to combine your release and push build scripts and make use of the environment variables like MVO_EVENT.


Go mod takes care of dependencies. Just run the following for building mvoCI, and place it together with the necessary assets inside the dist-folder.

make dist



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

  • PostgreSQL
  • MySQL / MariaDB
  • SQLServer
  • SQLite3

Set up

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

Configuration and Usage


Config-file in JSON-format. See core/config.go.

Lock down

Do not execute mvoCI as root. It should be used with as little permissions as possible, but enough to be useful for your usecase. Most builds execute untrusted code like automake scripts, Makefiles or the like - make sure, that this untrusted code cannot leak information from your system.


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



Feel free to contribute to mvoCI if there are features missing for your use case. Either send me write-up for your use case, then I'll evaluate if it is inline with my goals of mvoCI. Feel also free to send pull-requests or patches my way.

If you want to start, try adding new routes in web/routing.go, then fill the new route with content and a template in views/. You can also have a look in the REST-API (web/api.go) code and add new functions there, which might be useful or add new hook-code for other git-version control systems (hooks/).

Project Structure

  • main.go - start point, reads config, starts builders, hands control to echo
  • core/ - database, configuration, logging. Fundamental stuff.
  • build/ - build workers and starting of builds from the web-side.
  • web/ - routing "table" for echo, handlers for requests, most of them called by echo
  • hook/ - webhook-request definitions for parsing the requests more or less generically (see web/hook.go)