summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLaurent Bonnans <laurent.bonnans@here.com>2018-06-25 14:03:59 +0200
committerLaurent Bonnans <laurent.bonnans@here.com>2018-06-25 14:08:14 +0200
commit9278ad8c3322b9a3ec713ba86006e901bd824486 (patch)
treed6b72e68a2c800611b05d652ba23dd0bd915c26f
parenta3c960df21c5f820cd7aa592a449be667f65cf86 (diff)
downloadmeta-updater-9278ad8c3322b9a3ec713ba86006e901bd824486.tar.gz
Small doc about setting up Jenkins for meta-updater
-rw-r--r--scripts/ci/README.adoc14
1 files changed, 14 insertions, 0 deletions
diff --git a/scripts/ci/README.adoc b/scripts/ci/README.adoc
new file mode 100644
index 0000000..222982b
--- /dev/null
+++ b/scripts/ci/README.adoc
@@ -0,0 +1,14 @@
1= Jenkins setup for running meta-updater CI
2
3As bitbake is quite resource-hungry, there are some special steps that are
4needed to run Jenkins CI tasks:
5
6- docker should be installed and the `jenkins` unix user should belong to
7 the `docker` group
8- `/opt/jenkins` should exist and have `jenkins:jenkins` permissions, it
9 will be mapped as a volume on the same location in the docker build
10 container
11
12Note that for nodes running Jenkins slaves as a docker container, the
13`/opt/jenkins` directory must exist on the host system as well, with
14permissions matching the user and groupd ids in Jenkins' docker