cws
/
yoctobuild
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
3 Commits 1 Branch 0 Tags 10 KiB
Go 100%
Go to file
Chris Sexton ddab63e384 Fixes #1: Add a mutex to prevent multiple builds 2015-04-16 21:48:03 -04:00
badges initial commit 2015-04-14 11:44:16 -04:00
.gitignore initial commit 2015-04-14 11:44:16 -04:00
AUTHORS Add a license file 2015-04-14 21:16:10 -04:00
LICENSE Add a license file 2015-04-14 21:16:10 -04:00
README.md initial commit 2015-04-14 11:44:16 -04:00
config.json initial commit 2015-04-14 11:44:16 -04:00
yoctobuild.go Fixes #1: Add a mutex to prevent multiple builds 2015-04-16 21:48:03 -04:00

README.md

yoctoBuild

yoctoBuild is a bare-bones build service for your personal projects. Since many hosted build services do not work outside of GitHub and BitBucket, this was made to work with Gogs for light usage where hosting Jenkins would be absurd.

yoctoBuild is unaware of git, Mercurial, scss, etc. It depends on a bash executable and proper configuration.

Usage

Run yoctobuild in its directory or copy the badges and a config file to a working directory. Provide a -secret on startup, and then set your Gogs/Git hooks/etc to send a request to /projects/<your project>/build?secret=<your secret>.

The config file consists of a map of projects and their steps. The build server does nothing but create a working directory for the build so the build steps must check out code, perform tests, and manage any dependencies. The config file should only be modified by owners of the server it lives on as it may execute arbitrary commands on your behalf.

This build service is very simple. It does not watch for branches or anything of the like. You must configure a project for each individual item that you wish to watch.

Badges may be served by embedding /projects/<your project>/badge as an image in your page.