Jenkins CI Server
URLs
The openpetra-Jenkin-Servers can be found on
Ubuntu
- installed on Ubuntu 11.10 (Oneiric Ocelot)
apt-get remove apache bind9
Mono
- using Mono 2.10 for best support for c# 4.0 etc
apt-get install mono-runtime mono-xbuild mono-gmcs
- for msgfmt to work for the i18n, processing of language files, you need to run:
ln -s /usr/bin/gmcs /usr/bin/mcs
other development tools
apt-get install bzr doxygen graphviz sqlite3 postgresql libpg-java dos2unix fakeroot lintian nsis
setup SchemaSpy
- Download SchemaSpy_5.0.0.jar from http://schemaspy.sourceforge.net/
cd /var/tmp/OpenPetraBuild
vi /etc/postgresql/9.1/main/pg_hba.conf and add at top: local all petraserver md5
nant recreateDatabase resetDatabase -D:DBMS.Type=postgresql
java -jar schemaSpy_5.0.0.jar -t pgsql -dp /usr/share/java/postgresql-jdbc4.jar -host localhost:5432 -db openpetra -u petraserver -p petra -s public -o outputDir
NAnt
- apt-get install nant
- then download latest NAnt, NAnt 0.91 Release
- unpack tar.gz file to /usr/local/nant-0.91
- modify /usr/bin/nant and point at /usr/local/nant-0.91/bin/NAnt.exe
- somehow, there is a problem when building for mono-2.0 or mono-4.0. The solution is to have two NAnt profiles:
the default/usr
and the other is/usr/local/nant-for-4.0
/usr/bin/nant:
#!/bin/sh #exec /usr/bin/cli /usr/lib/NAnt/NAnt.exe "$@" mono --runtime=v2.0 /usr/local/nant-0.91/bin/NAnt.exe "$@"
/usr/local/nant-for-4.0/bin/nant:
#!/bin/sh #exec /usr/bin/cli /usr/lib/NAnt/NAnt.exe "$@" mono --runtime=v4.0 /usr/local/nant-0.91/bin/NAnt.exe "$@"
Jenkins
wget -q -O - http://pkg.jenkins-ci.org/debian-stable/jenkins-ci.org.key | sudo apt-key add - vi /etc/apt/sources.list: deb http://pkg.jenkins-ci.org/debian-stable binary/
apt-get update apt-get install jenkins
- change port to 80: https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu
- better to use lighttpd because Apache needs another 200 MB of RAM.
- /etc/lighttpd/lighttpd.conf
add mod_proxy to the server.modules list, and at the bottom: proxy.server = ( "/" => (( "host" => "127.0.0.1", "port" => 8080)), )
- installed plugins:
backup
see also https://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins
tar czf jenkins.tar.gz --exclude '/var/lib/jenkins/jobs/OpenPetraCodeDoc/javadoc/*' --exclude '/var/lib/jenkins/jobs/OpenPetraCodeDoc/schemaSpy/*' /var/lib/jenkins/
Jenkins on Windows
Running at: http://ci-win.solidcharity.com/
Installation
- Jenkins
- Version 1.475 got installed
- downloaded from http://mirrors.jenkins-ci.org/windows/
- Install it so that Jenkins runs as a Windows Service. See [7] for details.
- Ensure the CheckBox ‘Allow service to interact with desktop’ is ticked (this is not ticked by default) on the Properties Window of the 'Jenkins' Service (found in the Windows Control Panel 'Services' applet) - on the 'Log On' Tab. This is necessary for certain NUnit Forms tests to succeed! (If this is not ticked, certain NUnit Forms tests (e.g. at the time of writing: 11 Tests in
Tests.MFinance.Client.ExchangeRates.TCorporateExchangeRateTest
) will fail when run as a Jenkins Build job.)
- Ensure the CheckBox ‘Allow service to interact with desktop’ is ticked (this is not ticked by default) on the Properties Window of the 'Jenkins' Service (found in the Windows Control Panel 'Services' applet) - on the 'Log On' Tab. This is necessary for certain NUnit Forms tests to succeed! (If this is not ticked, certain NUnit Forms tests (e.g. at the time of writing: 11 Tests in
- Version 1.475 got installed
- Bazaar for Windows
- Version 2.4.2 got installed
- downloaded from: https://launchpadlibrarian.net/84264368/bzr-2.4.2-1-setup.exe
- no need to install TortoiseBzr
- Version 2.4.2 got installed
- Our own packaged NAnt installer for NAnt 0.92
- .NET 4 Framework (Full)
- Windows Software Development Kit (SDK) for Windows 7 and .NET Framework 4
- downloaded from: http://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/winsdk_web.exe
- installed only the bits under '.NET Development' and 'Microsoft Visual C++ 2010'
- PostgreSQL 9.1
- after installation follow steps on http://sourceforge.net/apps/mediawiki/openpetraorg/index.php?title=Notes_about_PostgreSQL
- BUT: create a DB with name 'buildserver' instead of 'petra' and a user called 'buildserver' instead of a user with your Windows user name. The password that you specify for the user 'buildserver' needs to be put into the OpenPetra.build.config file, property 'DBMS.Password' (see next section)!
- Version 9.1.7.1 x64 got installed
- after installation follow steps on http://sourceforge.net/apps/mediawiki/openpetraorg/index.php?title=Notes_about_PostgreSQL
- Poedit
- Version 1.5.4 got installed
- InnoSetup 5
- Version 5.5.2 (Unicode) got installed
- http://files.jrsoftware.org/is/5/isetup-5.5.2-unicode.exe
- during installation an option is given to install the 'Inno Setup Preprocessor'. That should be installed (is ticked by default).
- Version 5.5.2 (Unicode) got installed
- NUnit 2.6
- Version 2.6.0.12051 got installed
- Select 'Typical installation' during the installation.
Configuration
there is only one OpenPetra.build.config file which is valid for all jobs, stored in eg. C:\Program Files (x86)\Jenkins\workspace\OpenPetra.build.config
<?xml version="1.0"?> <project name="OpenPetra-userconfig">
<property name="PostgreSQL.Version" value="9.1"/> <property name="DBMS.DBHostOrFile" value="devdb.solidcharity.com"/> <property name="DBMS.DBName" value="buildserver"/> <property name="DBMS.Setup.DBName" value="openpetra_basedb2"/> <property name="DBMS.UserName" value="buildserver"/> <property name="DBMS.Password" value="???"/> <property name="Server.DebugLevel" value="0"/> <property name="Server.Port" value="9432" /> </project>
Nightly Builds for Translators
Jenkins can also be a help translating openpetra. By this, translators can work on a translation online and on the next day get an installer including already their translated items. This makes it easier for translators because then they can see their translations right away.
You can get the Nightly Build here. Please download the exe-file OpenPetraSetup-x.x.xx.xxxx.exe and install it on your computer to see your new translations.
Further Information
- exporting translations to a bazaar branch
- conversion tool from Inno Setup to NSIS scripts
- other option running wine in order to run InnoSetup on Linux. (This seems to be more complicated to me(Joachim) as there are several points where this way would fail. For example Xvfb (or ttydrv) would be needed as InnoSetup wants to use an X Window.)
- installer on jenkins
- (We tried "Nullsoft Install" for building Windows Installers but due to some complications there's now running aswell a windows-Jenkins which uses InnoSetup to build the windows Installer.)