jenkins: add notes about setting up a build slave
authorJustus Winter <justus@g10code.com>
Wed, 8 Mar 2017 16:37:16 +0000 (17:37 +0100)
committerJustus Winter <justus@g10code.com>
Wed, 8 Mar 2017 16:37:16 +0000 (17:37 +0100)
misc/jenkins/README.org
misc/jenkins/bin/jenkins-slave.dist [new file with mode: 0755]

index bda32a3..b6be452 100644 (file)
@@ -1,4 +1,25 @@
 * Notes
+** Setting up a Jenkins build slave
+ - install a jre, make, autoconf, automake, libtool, gcc, git, bison,
+   fig2dev, ghostscript, gnutls, sqlite3, pkg-config, imagemagick
+ - create a user jenkins
+ - clone gnupg-doc
+   $ git clone git://git.gnupg.org/gnupg-doc.git
+ - link ~/bin
+   $ ln -s gnupg-doc/misc/jenkins/bin
+ - download slave.jar
+   $ wget https://jenkins.gnupg.org/jnlpJars/slave.jar -O bin/slave.jar
+ - copy and adapt launcher
+   $ cp bin/jenkins-slave.dist bin/jenkins-slave
+ - make sure that jenkins@soro can ssh to the new node
+ - go to https://jenkins.gnupg.org/computer/new and copy an existing
+   configuration, adapting it as needed
+ - setup 'GPGME tests for GnuPG' as described below
+ - for each project, add the new nodes distinct label to the
+   configuration matrix, and force a rebuild.  Start with libgpg-error
+   and walk your way up the dependency chain:
+   - libgpg-error, libnpth, libassuan, libksba, libgcrypt, ntbtls,
+     gnupg, gpgme
 ** GPGME tests for GnuPG
 There is a reasonably up-to-date (but this is currently a manual
 process) GPGME source at
diff --git a/misc/jenkins/bin/jenkins-slave.dist b/misc/jenkins/bin/jenkins-slave.dist
new file mode 100755 (executable)
index 0000000..1d9afad
--- /dev/null
@@ -0,0 +1,9 @@
+#!/bin/sh
+
+set -x
+
+[ -f ~/.profile ] && . ~/.profile
+uname -a
+env
+
+exec java -jar ~/bin/slave.jar