gluon/contrib/ci/jenkins-community-slave
2019-09-28 00:56:53 +02:00
..
Dockerfile contrib: fix inheritance of jenkins-community-slave dockerfile (#1831) 2019-09-28 00:56:53 +02:00
README.md contrib: Set up continuous integration through Jenkins 2019-09-26 16:12:09 +02:00
slave.py contrib: Set up continuous integration through Jenkins 2019-09-26 16:12:09 +02:00

Gluon CI using Jenkins

Requirements

  • Only a host with docker.

Architecture

Screenshot from 2019-09-24 00-20-32

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:
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/
docker run --detach --restart always \
    -e "SLAVE_NAME=whoareyou" \
    -e "SLAVE_SECRET=changeme" \
    -v /var/cache/openwrt_dl_cache/:/dl_cache
  1. Check whether the instance is running correctly:
    • Your node should appear here.
    • When clicking on it, Jenkins should state "Agent is connected." like here: Screenshot from 2019-09-24 01-00-52
  2. Your docker container needs to be rebuilt, when the build dependencies of gluon change. So please be aware of that and update your docker container in that case.

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.