FlightGear build server: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
No edit summary
Line 60: Line 60:


=== Linux ===
=== Linux ===
This is the Linux slave. In reality it is the same machine than ''master'' but with another login. That's why we want the SSH connection on ''localhost''.
This is the Linux slave based on Fedora 21. In reality it is the same machine than ''master'' but with another login. That's why we want the SSH connection on ''localhost''.


This slave is configured to work in /home/jenkins, that's where we have plenty of free space disk on this machine.
This slave is configured to work in /home/jenkins, that's where we have plenty of free space disk on this machine.

Revision as of 21:05, 21 February 2015


What is it ?

FlightGear build server is a system based on Jenkins who help core developpers to check that their source code is correct for all OS.

For example, some core developpers are working with Linux and have no access to a Windows installation in order to test if what they have implemented for Linux will works for Windows and even Mac.

The build server will automatically start a new compilation after every commits pushed in the source code. We have the ability to compile the source code for Linux, Windows and Mac.

He is also responsible for building release package for Linux, Windows and Mac.

FlightGear build server is available at: http://build.flightgear.org:8080


Users info

As a user you can help developpers to track bugs from the latest source code, by tracking bugs you would report them on the mailing list or bug tracker (not the forums).

But take care to mention that you're using a nightly build, and to specify when it was built (you can find details in FlightGear's Help > About dialog):

About-dlg-2.10.png

If you are interested in this job you want to follow these instructions:

Linux

Well, unfortunately there is nothing interesting for you here :)

Because Linux users have a powerful tools to compile and use the latest cource code, give a look at Scripted_Compilation_on_Linux_Debian/Ubuntu

Mac

You need 2 things to run the latest source code: the compiled source code and the data.


You can download the compiled source code at: FlightGear Mac nightly build

You can download the data with git: git clone https://git.gitorious.org/fg/fgdata.git

Windows

You need 2 things to run the latest source code: the compiled source code and the data.


You can download the compiled source code at: FlightGear Windows nightly build

You can download the data with git: git clone https://git.gitorious.org/fg/fgdata.git


Developpers info

Here is a brief summary about the configuration of Jenkins.

If need anything you would contact either James, Gene or Clément (the mailing list is a good place to contact them if you don't know where to look at them)

master

The master is the processus who manage the distribution of build among slaves.

Basically, his job is to be connected to his slaves and ask them to execute jobs who have been configured.

Linux

This is the Linux slave based on Fedora 21. In reality it is the same machine than master but with another login. That's why we want the SSH connection on localhost.

This slave is configured to work in /home/jenkins, that's where we have plenty of free space disk on this machine.

Mac

This is the Mac slave.

Windows

This is the Windows slave. He is located in the same LAN than master/Linux slave. There is MSVC2010 installed.

This slave is configured to work in G:\jenkins, that's where we have plenty of free space disk on this machine.


Release process

The Linux slave has the responsability to provide the base-package for the Linux-release and Windows-release job.

Because the Linux and Windows slave are in the same LAN it's not a problem to exchange 1GB on the network.


Windows-release, Mac-release and Linux-release have to be triggered by-hand. The result is automatically uploaded to http://fgfs.goneabitbursar.com/releases/