2019-09-26 14:12:09 +00:00
# Gluon CI using Jenkins
## Requirements
2020-03-22 17:49:22 +00:00
- Linux system
- with docker installed
- with Hardware Virtualisation (KVM Support)
- Verify using: `lscpu | grep vmx`
- If machine is virtualized host needs to load `kvm_intel` with `nested=1` option and cpuflags need to include `vmx`
2019-09-26 14:12:09 +00:00
## Architecture
## Installation
You can support the gluon CI with your infrastructure:
1. You need to query @lemoer (freifunk@irrelefant.net) for credentials.
2. He will give you a `SLAVE_NAME` and a `SLAVE_SECRET` for your host.
3. Then go to your docker host and substitute the values for `SLAVE_NAME` and a `SLAVE_SECRET` in the following statements:
``` shell
git clone https://github.com/freifunk-gluon/gluon/
cd gluon/contrib/ci/jenkins-community-slave/
docker build -t gluon-jenkins .
mkdir /var/cache/openwrt_dl_cache/
2020-04-07 13:45:34 +00:00
chown 1000:1000 /var/cache/openwrt_dl_cache
2019-09-26 14:12:09 +00:00
docker run --detach --restart always \
2020-03-22 17:49:22 +00:00
--env "SLAVE_NAME=whoareyou" \
--env "SLAVE_SECRET=changeme" \
--device /dev/kvm:/dev/kvm \
--volume /var/cache/openwrt_dl_cache/:/dl_cache \
gluon-jenkins
2019-09-26 14:12:09 +00:00
```
4. Check whether the instance is running correctly:
- Your node should appear [here ](https://build.ffh.zone/label/gluon-docker/ ).
- When clicking on it, Jenkins should state "Agent is connected." like here:
2020-01-18 18:32:00 +00:00
5. **Your docker container needs to be rebuilt, when the build dependencies of gluon change. As soon as build dependencies have changed, the build dependency api level has to be raised.** After you rebuilt your docker container, notifiy @lemoer , so he can bump the versioning number.
2019-09-26 14:12:09 +00:00
## Backoff
- If @lemoer is not reachable, please be patient at first if possible. Otherwise contact info@hannover.freifunk.net or join the channel `#freifunkh` on hackint.
