2015-09-19 12:50:22 +00:00
|
|
|
###
|
|
|
|
|
### LAMINAR_HOME
|
|
|
|
|
###
|
|
|
|
|
### Root location containing laminar configuration, database,
|
|
|
|
|
### build workspaces and archive.
|
|
|
|
|
###
|
|
|
|
|
### Default: /var/lib/laminar
|
|
|
|
|
###
|
2015-09-19 13:29:07 +00:00
|
|
|
#LAMINAR_HOME=/var/lib/laminar
|
|
|
|
|
|
2015-09-26 20:54:27 +00:00
|
|
|
###
|
|
|
|
|
### LAMINAR_TITLE
|
|
|
|
|
###
|
|
|
|
|
### Page title to show in web frontend
|
|
|
|
|
###
|
|
|
|
|
#LAMINAR_TITLE=
|
|
|
|
|
|
2015-09-19 13:29:07 +00:00
|
|
|
###
|
|
|
|
|
### LAMINAR_KEEP_WORKDIR
|
|
|
|
|
###
|
|
|
|
|
### If set (to anything), the job workdir $LAMINAR_HOME/run/$JOB/$NUM
|
|
|
|
|
### will not be deleted after the run has completed
|
|
|
|
|
###
|
|
|
|
|
#LAMINAR_KEEP_WORKDIR=1
|
2015-09-19 15:24:20 +00:00
|
|
|
|
|
|
|
|
###
|
|
|
|
|
### LAMINAR_ARCHIVE_URL
|
|
|
|
|
###
|
|
|
|
|
### Base url used to request artifacts. Laminar can serve build
|
|
|
|
|
### artifacts (and it will if you leave this unset), but it
|
|
|
|
|
### uses a very naive and inefficient method. Best to let a real
|
|
|
|
|
### webserver handle serving those requests.
|
|
|
|
|
###
|
|
|
|
|
#LAMINAR_ARCHIVE_URL=http://backbone.example.com/ci/archive
|
