Monday, October 14, 2019

Setup a Github Triggered Build Machine for an Eclipse Project

Disclaimer 1: This blog post literally is a "web log", i.e., it is my log about setting up a Jenkins machine with a job that is triggered on a Github pull request. A lot of parts have been described elsewhere, and I link to the sources I used here. I also know that nowadays (e.g., new Eclipse build infrastructure) you usually do that via docker -- but then you need to configure docker, in which case you will need the same knowledge. However, since this describes a full setup for building an Eclipse project via Jenkins, it might be interesting to others as well.

Disclaimer 2: Setting up a continuous integration pipeline (which we will do here) is a kind of DevOps job. One problem with devops is that, as in my case, developers often do not have that much operations knowledge. So if some operator finds any silly things here, please leave me a comment -- I'm eager to learn.


Why did I need a Github triggered build in the first place? I'm working as a professor at the Hamburg University of Applied Sciences, teaching programming, software engineering and computer science stuff in general. I am currently teaching a special class at the university: the “Eclipse N4JS project”. In this kind of class, which students in the 5th semester are supposed to attend, the students are expected to do a more real project. These projects are derived from research, e.g. cyber systems or autonomous cars. In my case, they have to work on a really real project: Eclipse N4JS. The students become a Scrum team (9 people), and they are working on smaller yet real-world tasks.

Since Eclipse N4JS is a real programming language used in production for a couple of years yet, it seems very risky to let students work on that stuff. Even more if you know that the Eclipse N4JS IDE nightly build is actually used in production. This is only possible because we have a very extensive test suit with 94.920 tests.

So, the students are eventually supposed to do real pull-request. For that I needed to set up a Jenkins job running all tests on that pull-requests in order to assure that it can be merged to master without breaking anything. This blog post is my log how I set up that server.

Setup a Github triggered build machine

In the following, I describe how to setup a Linux (Ubuntu 18.04.3 LTS) machine with all required software, in particular Jenkins, and how to configure Github etc., to start a build whenever a pull request is created against a repository. The pull request performs a pre-merge, that is, it runs your build with the pull request already merged to master (for the build only)! In short, we will

  • install Java, Maven, and Jenkins
  • install some JavaScript software (needed for smee client)
  • setup Github to trigger our build (via
  • install Xvnc to enable UI tests
  • write a Jenkins build file eventually running our maven build (for Eclipse N4JS)


I roughly followed "Automated Jenkins builds on GitHub pull request" by Karolis


I have a dedicated Linux Ubuntu 18.04.3 LTS machine (16 GB memory for my large test suite :-) ) set up on a VM (done by my friendly admin Peter R. -- thank you!). In order to be able to use english descriptions etc., I switched to english and also adjusted some language settings accordingly:

First, switch to english:

sudo vi /etc/default/locale
Changed this file to

You also need the admin to enable port 8080 on your machine, so that others can reach it in case you are behind a firewall. We will install Jenkins to listen to port 8080. Of course, you can use any other port.

Install required fundamental software

First we install some software that is kind of fundamental: git, java, maven, and ant.

  1. Install git, if it is not installed yet:
    sudo apt install git
  2. Install Java 11:
    sudo apt install openjdk-11-jdk-headless
    Note: Java 11 is support by Jenkins since 2.164. We need the JDK, since Jenkins needs a JDK! Ensure that the path exists:
    JAVA_HOME: /usr/lib/jvm/java-11-openjdk-amd64
  3. Install Maven and Ant:
    sudo apt install maven
    sudo apt install ant
    Check version and maven home:
    mvn --version
    ant -version
    This will printout something like
    Apache Maven 3.6.0
    Maven home: /usr/share/maven 
    Apache Ant(TM) version 1.10.5 compiled on March 28 2019 
    Note that ant is installed to /usr/share/ant-- although you probably do not need that path later on.

    Alternatively you could install them manually, e.g.

    sudo apt install unzip
    wget ""
    sudo mv apache-maven-3.6.1 /opt/
    wget ""
    mv apache-ant-1.9.14 /opt/
    Note that you need to add the path to the bin files of Maven and Ant to the PATH in scripts started later.
  4. In order to be able to install the Smee client later on, you need node.js (and npm). There are some hints found at nodesource's github page.
    sudo apt install curl
    curl -sL | sudo -E bash -
    sudo apt-get install -y nodejs
  5. In my case, I also needed yarn. This is only needed by my build (i.e. the tests), so you could skip that step if you do not need yarn. There is an issue which you might run into (as I did), described in a Yarn Github issue 2821. Thus, ensure the right yarn is installed: If calling yarn emits ERROR: There are no scenarios; must have at least one. do the following:
    sudo apt remove cmdtest 
    curl -sS | sudo apt-key add -
    echo "deb stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
    sudo apt update
    sudo apt install yarn

Setup Smee and Smee client

If you are not admin of your Github repository, and if you do not want to drill to many holes in your firewall, then you probably need is a "Webhook payload delivery service". That is, you tell Github to send events to, and you can use the Smee client to retrieve the these events and forward them internally.


  1. Setup a channel at, simply by clicking "start new channel" at Write down the URL you get there, as this is the URL you need to configure at github.
  2. Install Smee client on your build machine.
    sudo npm install --global smee-client
    I assume the following warning can be ignore, since smee is now in version 5.1: Warning: superagent@3.8.3: by default, therefore you may need to add it yourself (e.g. GitHub blocks requests without a User-Agent header). This notice will go away with v5.0.2+ once it is released. Note that /usr/bin/smee actually is located at /usr/lib/node_modules/smee-client/bin/smee.js.
  3. With this client, you then configure the internal fowarding of the event, i.e.
    smee -u --path /github-webhook/ --port 8080
    This is the theory. In practice you want at least to run smee as a service. So this is what we do in this setp: set up smee as service We write a init script and a systemctl service description for that. Here is /etc/init.d/smee
    #! /bin/sh
    test -x $DAEMON || exit 0
    . /lib/lsb/init-functions
    case "$1" in
     log_daemon_msg "Starting smee" "smee"
     start_daemon -p $PIDFILE $DAEMON
     log_end_msg $?
     log_daemon_msg "Stopping smee" "smee"
     killproc -p $PIDFILE $DAEMON
     log_end_msg $?
        $0 stop
        $0 start
        status_of_proc -p $PIDFILE $DAEMON atd && exit 0 || exit $?
        echo "Usage: /etc/init.d/smee {start|stop|restart|force-reload|status}"
        exit 1
    exit 0
    Additionally you need the /etc/systemd/system/smee.service file. This contains the fowarding with your URL
    [Unit] webhook delivery for my build
    ExecStart=/usr/bin/smee -u«YOUR SMEE PATH» --path /github-webhook/ --port 8080
    In order to start smee, call it similar to jenkins:
    sudo /etc/init.d/smee start
    In order to check if it worked, call
    sudo /etc/init.d/smee status
    This should output something similar to
    smee.service - webhook delivery for my build
       Loaded: loaded (/etc/systemd/system/smee.service; disabled; vendor preset: enabled)
       Active: active (running) since Thu 2019-08-22 07:04:29 UTC; 7min ago
     Main PID: 15314 (node)
        Tasks: 11 (limit: 4915)
       CGroup: /system.slice/smee.service
               └─15314 node /usr/bin/smee -u --path /github-webhook/ --port 8080
    Aug 22 07:04:29 ... systemd[1]: Started webhook delivery for my build
    Aug 22 07:04:29 ... smee[15314]: Forwarding to
    Aug 22 07:04:30 ... smee[15314]: Connected
    You may also use sudo journalctl -u smee (or add an -f for realtime reporting) checking the output in the systemctl log -- this will then also display the events smee received from the Github webhook!

    Note that if you are playing around, you may need to stop it via sudo /etc/init.d/smee stop.

See below for some troubleshooting hints.


If you are the admin of the github repository, you can adjust the event being sent to your Jenkins via Since I am not the admin, I would have to write a bug report every time I want to adjust something. Besides, the settings provided by GitHub do not fit my needs: I want to have events for all push events, and I want to have an update when a new pull request has been opened. I did not find any setting for that on GitHub -- the "only push events" does not send anything when a new pull request has been opened.

When you get all events, your Jenkins starts too many jobs. E.g., a job is triggered only if someone wrote a comment. For that reason, I wrote a small script acting as a proxy between the smee client and Jenkins. This proxy, called GHEF for "GitHub Event Filter", only forwards push and pull-request opened events to Jenkins. The script is written in JavaScript, and it is to be installed similarly as the smee client. It needs to be installed via

sudo npm install --global ghef
I run GHEF on port 3000, thus, smee forwards to 3000. GHEF then forwards to port 8080 (i.e. Jenkins).

You then need to provide init script also similar to the smee client. So, the events are processed as follows:

  1. GitHub emits event to
  2. The smee client gets the event from, forwarding it to GHEF
  3. GHEF processes the event, in case of push or pull-request opened it is forwared to Jenkins, otherwise ignore
  4. Jenkins finally gets the event, and the GitHub plugin triggers a build
The syslog shows this process:
systemd[1]: Started GitHub Event Filter for N4JS webhook.
ghef[28779]: GitHub Event Filter 0.0.5 listening on port 3000, forwarding to localhost:8080!
ghef[26459]:   Ignoring github event: create
Oct 29 12:26:40 projn4js smee[21884]: POST - 200
Oct 29 12:30:44 projn4js ghef[26459]: Forwarding #1534 github event: pull_request, action: opened
Oct 29 12:30:44 projn4js smee[21884]: POST - 200
Oct 29 12:30:46 projn4js ghef[26459]:   Ignoring github event: status
Oct 29 12:30:46 projn4js smee[21884]: POST - 200
Note that port 3000 is only available locally.

Prepare GitHub

Add Webhook

At Go to Settings > Webhooks
  • Payload URL:«YOUR SMEE PATH»
  • Content Type: application/json
  • no secret
  • Send me everthing
If you are not admin of your repository, e.g., in case of an Eclipse project, you need to file a bugzilla. In this bugzilla, tell the admin your Smee URL. Note that you need to use your own Github account to access the repository, see next section.

Create Token

In order to enable your build to communicate with the Github API, credentials are required. This is done by creating a Github API token with the right credentials.

Goto Personal access tokens at GitHub.

The following rights are required (maybe less, please drop me comment if you know details!):

- repo
- repo:status
-  repos_deployment
-  public_repo
- write:packages
- read:packages
- admin:org
 - write:org
 - read:org
- notifications 
- admin:public_key
 - read:public_key
- admin:repo_hook
 - read:repo_hook
- write:discussion
 - read:discussion
This token is used as password when you set up the GitHub organization!

Install Jenkins on Ubuntu

We are now ready to install Jenkins.


For that, I also had a look at the following descriptions:


  1. Install Jenkins:
    wget -q -O - | sudo apt-key add -
    sudo sh -c 'echo deb binary/ > /etc/apt/sources.list.d/jenkins.list'
    sudo apt-get update
    sudo apt-get install jenkins
    I got an error: jenkins : Depends: daemon but it is not installable Solved this by running
    sudo add-apt-repository universe
    and then
    sudo apt-get install jenkins
    again. This installed Jenkins 2.176.2 (note: Java 11 support since 2.164) In order to find out where everything has been installed, have a look at /etc/default/jenkins -- in this file, all settings are defined.
  2. Check that Jenkins is running:
    systemctl status jenkins
    and in general control Jenkins via
    sudo /etc/init.d/jenkins restart
    Usage: /etc/init.d/jenkins {start|stop|status|restart|force-reload}
  3. Log in the first time with initial password. The initial password can be found via
    sudo cat /var/lib/jenkins/secrets/initialAdminPassword
    Then open your Jenkins (http:\\yourserver:8080) with this password. Note: I got a security exception, probably due to an interrupted first start. Fix explained on stackoverflow did not work, since the config file is overridden. You may fix this from the web interface. I removed Jenkins (and removed the /var/lib/jenkins folder) and reinstalled it.
  4. Install suggested plugins
  5. Created new admin user.
  6. Setup global tools, that is, Java, Maven and Ant. For that, goto Manage Jenkins > Global Tool Configuration in your Jenkins web UI and setup these tools accordingly:
    1. setup JDK: Manage Jenkins > Global Tool Configuration with JAVA_HOME as listed above
    2. Maven and ant may be installed automatically (using name mvn and ant), or you configure them using the paths of your installation above. the important thing is to use the correct name, in my case mvn and ant.


Since I need to run UI tests, I needed a virtual display. Actually, this was the hardest part of the setup, and unfortunately I did not find much help on the internet.


There are some descriptions available.
  1. Xvnc Jenkins Plugin Page
  2. "Continuous Integration with Hudson/Jenkins" from the LSDevLinux team


  1. Install xvnc:
    sudo apt-get install vnc4server fluxbox
    sudo su - jenkins
    pass: xxxxxxxx (doesn't matter)
    The password, logs, and xstartup script are all found at /var/lib/jenkins/.vnc. This is the place to look in case of problems.

    Alas this did not work, in the log file (e.g., /var/lib/jenkins/.vnc/«servername»:«displaynumber».log) I found the line /var/lib/jenkins/.vnc/xstartup: x-terminal-emulator: not found

    For the UI tests, you do not need a terminal emulator, so just remove the line starting xterm from the xstartup script.

    I also had to create a file .Xmodmap in /var/lib/jenkins. I did this as user jenkins (sudo -su - jenkins) and simply touched (touch .Xmodmap)it. Also see notes below (if something is not working...)

    Eventually I ended up with the following startup script:

    [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
    [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
    vncconfig -iconic &
    (and everything else commented out)

    Note that there is an alternative VNC, TigerVNC. I also tried that one, since it is the one installed on the old Eclipse build infrastructure. But I changed back to vnc4server (since I got the same problems with TigerVNC...).

  2. Install xvnc plugin via Jenkins plugin manager.
  3. This step I only added later, I am not quite sure if it is actually required. When I compared my build output with the output of a build which was working, I noticed that the vncserver is started slightly differently. So I configured the vncstartup in the global Jenkins configuration, i.e. I set the vncserver command line to
    /usr/bin/vncserver :$DISPLAY_NUMBER -geometry 1024x768 -depth 24 -ac -noreset

    This should do the trick, unfortunately I run into problems. That is, my tests were not able to connect to the virtual display. I still do not really know why, and the internet was not helpful at this point (if you know a good description, let me know!). There are a couple of possible things that can go wrong: vncserver is not starting correctly or is immediately shutdown, security settings are wrong, or -- as I figured out eventually -- the global environment variable DISPLAY is not correctly forwarded to your test.

    Due to these problems I was not able to successfully run my UI tests. I tried a lot, and I even installed even Gnome in my desperation. This caused my vncserver to not even start anymore with a XIO: fatal IO error 11 (Resource temporarily unavailable) on X server... in my logs. I then uninstalled Gnome (sudo apt-get remove gnome), which did not fix that problem, removed and re-installed vnc4server and Fluxbox. Did not work. Eventually, after removing gdm and gnome-settings-daemon, and after reconfiguring vnc4server and Fluxbox (sudo dpkg-reconfigure fluxbox and sudo dpkg-reconfigure vnc4server) it worked again.

Setup Pipeline

Back to the triggered build. You need the Github Jenkins plugin, if you have installed the recommended plugins on first start-up of Jenkins (see above), this is already installed.

We will set up a pipeline build on Jenkins, which is triggered (indirectly) via Github.


For this, I followed the following tutorials:


  1. Add a new credential via the Jenkins Web UI at Credentials> System > Global credentials (unrestricted). Use your GitHub user account and the previously created token as password.
  2. Create a new GitHub organization (which will then spawn jobs). Go to Jenkins > New Item > GitHub Organization. I got an exception here (Caused by: java.lang.NoClassDefFoundError: com/cloudbees/plugins/credentials/CredentialsProvider), similar to the one described as Jenkins issue 58071.
    • I tried to install the Blue Ocean plugin as this seems to fix the problem for some people. -- That did not help in my case.
    • Restarted Jenkins (sudo /etc/init.d/jenkins restart) helped, though!
  3. In the job, go to Configure and configure the job:
    • Credentials: user name with password, the password is the token!
    • Owner: eclipse (or whatever organization owns the repository)
    • Behaviors: Add > Filter by regex: «repository name» (since you do not want to get events for everything)
    • Discover pull requests from origin
      • Merging the pull request with the current target branch...
    • Discover pull requests from forks
      • Merging the pull request with the current target branch...
      • Trust: Nobody
    • Pipeline Jenkinsfile: «Name of your Jenkins file»
    The organization is scanned, the project is detected, with some PRs. Now, all what is left to do is to write the Jenkins file and merge it to your repository.


Actually, I did not write the following Jenkinsfile from scratch but reused the file used for my project (N4JS) on the Eclipse N4JS JIPP Instance. This file is found in the N4JS repository

However, I had to modify it a bit, due to a problem with my setup, see below for details.

 * Copyright (c) 2019 HAW Hamburg
 * All rights reserved. This program and the accompanying materials
 * are made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at
 * Based on eclipse-nightly.jenkinsfile
pipeline {
    agent any

    environment {
        NODEJS_PATH= '/usr/bin' // '/shared/common/node-v10.15.3-linux-x64/bin'
        YARN_PATH  = '/usr/bin' // '/shared/common/yarn/1.15.2/bin'
        MAVEN_OPTS = '-Xmx4G'
        JAVA_HOME  = '/usr/lib/jvm/java-11-openjdk-amd64'
        TIMESTAMP  = new Date().format("yyyyMMddHHmm")

    stages {
        stage('Build and Test') {
            steps {
                echo 'Starting Xvnc'
                wrap([$class: 'Xvnc', takeScreenshot: false, useXauthority: true]) {
                    echo 'Building and testing, using display ' + DISPLAY
                    script {
                     def envvars = [ 
                     ].join(' ')
                        def options = [
                            // for adjusting the script, maybe uncomment the following two lines:
                            '-DWORKSPACE=' + env.WORKSPACE,
                        ].join(' ')
                        def profiles = [

                        sh """\
                            git log -n 1
                            npm version
                        sh "mvn ${envvars} clean verify -P${profiles} ${options}"
                        // for tests, you may want to run less tests:
                        // sh "mvn clean verify ${options}"
                        // and for quick testing: only
                        // sh "mvn -o clean"

                      // sh "ls -Ral builds/"
                } // end wrap
            } // end steps
        } // end stage

    post {
        always {
            junit '**/surefire-reports/**/*.xml'
        cleanup {
            // Execute after every other post condition has been evaluated, regardless of status
            // See
            echo 'Cleaning up workspace'
            // Not today: deleteDir()
Some notes on the script:
  • In order to run UI tests, you need to run the tests with Xvnc running (see wrap ...).
  • In my case, it did not work because the DISPLAY environment variable was not correctly passed to the maven surefire tests. So I added the evnvars in the script and passed them to maven in the shell call. This took me several days to figure out!
One final note: Of course your build is only triggered if it find that Jenkinsfile, since we defined that earlier. The first time your build is then triggered should be the pull request in which you ask for merging the Jenkinsfile. And this is a great pull request for testing it :-)

When it works, you will be rewarded with a message at Github similar to this one:

Some hints in case something does not work

Do you get notifications?

In order to check that smee is really working, try the following:
// content of index.js
const http = require('http')
const port = 3000

const requestHandler = (request, response) => {
  response.end('Hello Node.js Server!')

const server = http.createServer(requestHandler)

server.listen(port, (err) => {
  if (err) {
    return console.log('something bad happened', err)

  console.log(`server is listening on ${port}`)
and then
smee -u«YOUR SMEE PATH» --path /github-webhook/ --port 3000
This should output any push on your system. Then stop that Smee and reuse the original one.

Emulate requests

Note that you can manually post requests to smee and see if it is working (so you do not need github for that) via
curl --header "Content-Type: application/json" --request POST --data '{ "key": "val" }'«YOUR SMEE PATH»
Easier: Or you can redeliver a request, either via Smee (on the Smee website) or Github (on the webhook settings).

Forgot your password?

In case you forgot your Jenkins admin password, have a look at this [stackoverflow thread][]. For the impatient reader: Update the password hash at /var/lib/jenkins/users/username/config.xml with
Once you have done this, just restart Jenkins and log in using this password: test. Of course, you need to change it ASAP!

Update Jenkins

You may get security warning on the management page http://«server»:8080/manage

In order to update Jenkins, follow these steps:

sudo apt-get update
sudo apt-get install jenkins
Jenkins will be restarted automatically. After that, update plugins in the update center. Simply select "compatibles" at the very bottom of the page and activate the uddate.

You may want to manually restart Jenkins after that via sudo /etc/init.d/jenkins restart.

Thanks: Thank you Yoosiba for some hints regarding my XVNC problem (and for writing the initial Jenkins-file for the Eclipse nightly)! And thank you, mmews-n4, for review.


Jörn Guy Süß said...

Hi Jens,
I would avoid this pain and Jenkins in particular. User Gitlab where this sort of job is conceptual and has a DSL to back it. You can read my reasoning here: The Death of Piecemeal CI/CD . Also: whenever you visit Australia please let me know. Happy to have you as a guest!
Best JG

Jens v.P. said...

@Jörn: Thanks for the comment (and the invitation to Australia :-) ). I know... Jenkins is kind of clumsy to use. However, the project I was using here is Eclipse N4JS, and at Eclipse, Jenkins is used and we already have all the scripts etc. written for the Jenkins-Maven/Tycho chain, even with Docker (which is not publicly available). This is why I reused these tools. At the university, we have Gitlab installed, and I'm looking forward to getting to know this better. And I'm curious whether UI tests would work out of the box then...