FlightGear build server

From FlightGear wiki
(Redirected from FlightGear Build Server)
Jump to navigation Jump to search

The FlightGear build server, sometimes called the nightly build server or just Jenkins, is a system based on Jenkins which helps core developers to check that their source code compiles correctly for all OS. It is also responsible for building release packages for Linux, Windows and Mac.


The output files on Jenkins download.flightgear.org and sf.net should always be the same. Jenkins pushes them to download.flightgear.org from where they get distributed to sf.net (with some renaming-magic involved). Direct dowloads from Jenkins should be avoided as much as possible. [1]

Some core developers 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 or Mac. The build server will automatically start a new compilation after each commit is pushed to the source code repository. We have the ability to compile the source code for Linux, Windows and Mac.

A "nightly build" is one that is automatically generated each night (hence the name) from the most recent code. Since it has not received as much testing as normal FlightGear versions, you might encounter some bugs; on the contrary, you get access to the latest-and-greatest features before they are officially released.


News (06/2015)

1rightarrow.png See Building FlightGear - Cross Compiling for the main article about this subject.

Cquote1.png mingw has came a long way, and i think the MXE openscenegraph package (currently at 3.2.1 on master!!), is beautifully maintained, now it builds almost all core libraries dynamically with some argument passing, even as a static target(MXE_TARGETS='i686-w64-mingw32.static'), but it's those plugins again, with their linking errors! i think these are because i'm using the i686-w64-mingw32.static-g++ compiler as opposed to the shared one...

so as soon as i can get the shared build environment running and solve all of it's dependancies for OSG, i think we can have a cross compiller in our hands!


SourceForge release candidate

As of 2018.1 release candidates are available from sourceforce https://sourceforge.net/projects/flightgear/files/release-candidate/ <https://sourceforge.net/projects/flightgear/files/release-candidate/>;

Where to find it

The FlightGear build server is available at: http://build.flightgear.org:8080/. There is no artifact available because we don't want copy +1GB to Jenkins master each days. This job is executed once per day.

You can get the artifact at {project infrastructure|buildserver}}

Cquote1.png We’ve improved the tool around daily build creation. Still some progress to be done but daily builds for Mac and Windows are uploaded to:

(And hence, all the SF mirrors)

And also directly available from:

http://download.flightgear.org/builds/nightly/ <http://download.flightgear.org/builds/nightly/>;

The ‘latest’ files in that directory are stable symlink, I am currently writing a descriptive web-page which will point to them since we expect the patch version number to evolve during 3.5 development (and I will be testing this soon, mostly to see what breaks!)

All the usual caveats about un-tested code apply - although we will probably add some warnings over time to the builds themselves (splash screen etc) to remind people they’re not using a stable release.

— James Turner (2015-03-23). [Flightgear-devel] Daily builds update.
(powered by Instant-Cquotes)

User info

The about dialog

As a user you can help developers 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).

Cquote1.png The GUI launcher included in these builds includes a new dialog to setup (and remember) the FGRoot using file picker. It does some version checking to hopefully make things as robust as possible for the user.
— James Turner (2015-03-26). Re: [Flightgear-devel] Download description page.
(powered by Instant-Cquotes)
Note  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)

If you are interested in doing this please follow these instructions:


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

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


You need two 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 git://git.code.sf.net/p/flightgear/fgdata/


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

Developer 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)


The master manages the distribution of builds among the slaves.

Basically, its job is to be connected to the slaves and ask them to execute the jobs which have been configured.


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 is the Mac slave.


This is the Windows slave based on Windows Server 2008. It 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 responsibility to provide the base-package for the Linux-release and Windows-release job.

Because the Linux and Windows slave are on the same LAN it is not a problem to exchange 1 GB 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/.