Jenkins CI Server: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
Line 1: Line 1:
==URLs==
==URLs==
The openpetra-Jenkin-Servers can be found on
There are no Jenkins Servers for OpenPetra anymore.
* http://ci.openpetra.org/ and
* http://ci-win.openpetra.org:8080/


== Linux Jenkins ==
== Linux Jenkins ==

Revision as of 20:52, 22 August 2018

URLs

There are no Jenkins Servers for OpenPetra anymore.

Linux Jenkins

Mono

other development tools

apt-get install bzr doxygen graphviz sqlite3 postgresql libpg-java dos2unix fakeroot lintian nsis

setup SchemaSpy

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

add mod_proxy to the server.modules list, and at the bottom:
proxy.server = (
   "/" => (( "host" => "127.0.0.1", "port" => 8080)),
)
  • installed plugins:
    • Bazaar Plugin [1]
    • Git Plugin [2]
    • DocLinks Plugin [3]
    • Email-ext Plugin [4]
    • Log Parser Plugin [5]
    • NAnt Plugin [6]
    • Build-timeout Plugin [7]
      • that Plugin is installed only on the Linux Build server. It stops a build after half an hour in case a build job runs amok...

gui tests in headless setup

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

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.)
Retrieved from ‘https://wiki.openpetra.org/index.php?title=Jenkins_CI_Server&oldid=4751’