JENKINS BUILD RADIATOR Installation and Set Up

JENKINS BUILD RADIATOR
Installation and set up

Document date: 11/01/2015

Author: Andrew White

FITNESSE

JENKINS

JENKINS configuration

INFORMATION RADIATOR

FITNESSE

+++++++++++++

create a fitnesse test

Fitnesse SimpleTest – code

#########################

!define TEST_SYSTEM {slim}

!define SLIM_VERSION {0.3}

!define SLIM_PORT {7777}

# SimpleTest

|eg.Division |

|numerator|denominator|quotient?|

|10 |2 |5.0 |

#######################

It is important to run this test now – in order to;
1. Check that it works

2. for fitnesse to create the necessary folder structure and xml files which Jenkins will utilise later

JENKINS

Jenkins monitors executions of repeated jobs, such as building a software project
download Jenkins from this url

choose | native package | windows

move the downloaded zip to; C:\development\jenkins

unzipping reveals a windows installer .msi and a setup.exe

click on the .msi (this is for a windows system)

run

Jenkins - take note of where Jenkins has installed to – this is very important. Because of Jenkins loading to port 8080, it means that Fitnesse has to have been loaded to port 8081.

Note also that Jenkins has probably loaded onto a chrome browser.

configure

############################

JENKINS configuration

Obtain these Jenkins plugins;

Within

1. Build Monitor View

2. Green Balls

3. fitnesse plugin

Extra Information on build monitor setup;

jenkins

create a build project

in SimpleTest configuration ‘build’ - ‘add build step’ ‘execute fitnesse tests’

ensure that all details are completed correctly (EG make sure all file paths are correct & timouts are set to ‘6000000’.

important

it is important to note that Jenkins picks up the xml to run fitnesse tests from the specified location in ‘path to fitnesse xml results file’. This path must be exactly the same file path in the ‘post build actions’ ‘path to fitnesse xml results file’

Create a notepad document & call it ‘jenkinsOutput.txt’ then rename it ‘jenkinsOutput.xml’

in this case;

C:\Fitnesse\FitNesseRoot\files\testResults\FrontPage.SimpleTest/jenkinsOutput.xml

The file path

In Jenkins it is important to also configure the xml file path for where to write the results when we do run the ‘jenkins invoked’ fitnesse test.

next it is important to add a ‘post build action’ of ‘publish fitnesse results report’

the file path must be exactly the same filepath as in the ‘Path to fitnesse xml results file’ – in this case;

C:\Fitnesse\FitNesseRoot\files\testResults\FrontPage.SimpleTest/jenkinsOutput.xml

press ‘apply’ press ‘save’

simple test ‘build now’

Click on the ‘build now’ link on the left of your screen – wait until build completes

build succeeded – as shown in ‘build history’

creating a build monitor view

go to ‘back to dashboard’

select the ‘+’ tab to the right of the ‘all’ tab

in this example we are going to show the results of the ‘SimpleTest’ test on the office information radiator (big screen)

click ‘ok’

tick the ‘SimpleTest’ tick box

click ‘apply’ & ‘ok’

INFORMATION RADIATOR

Use google chrome browser for your companies information radiator

url =

build monitor screen shows tests have passed (green) or failed (red)

important

it is important to stress again that Jenkins picks up the xml to run fitnesse tests from the specified location in ‘path to fitnesse xml results file’. This path must be exactly the same file path in the ‘post build actions’ ‘path to fitnesse xml results file’.

#######################