308
edits
FlightGear build server: Difference between revisions
added SF release candidate URL
(Fixes for old gitorious links by switching to {{fgdata clone}}.) |
(added SF release candidate URL) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Release}} | {{Release}} | ||
The '''FlightGear build server''', sometimes called the '''nightly build server''' or just '''Jenkins''', is a system based on [http://www.jenkins-ci.org 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 '''FlightGear build server''', sometimes called the '''nightly build server''' or just '''Jenkins''', is a system based on [http://www.jenkins-ci.org 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. | ||
{{Note| | |||
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. <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35539513/ | |||
|title = <nowiki> Re: [Flightgear-devel] [from forum] Torrenting FlightGear </nowiki> | |||
|author = <nowiki> Torsten Dreyer </nowiki> | |||
|date = Dec 8th, 2016 | |||
|added = Dec 8th, 2016 | |||
|script_version = 0.36 | |||
}}</ref> | |||
}} | |||
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. | 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. | ||
| Line 28: | Line 40: | ||
}} | }} | ||
}} | }} | ||
== 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/>;<br/> | |||
== Where to find it == | == Where to find it == | ||
The FlightGear build server is available at: {{build link}}. There is no artifact available because we don't want copy +1GB to Jenkins master each days. This job is executed once per day. | The FlightGear build server is available at: {{build link}}. 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}} | You can get the artifact at {project infrastructure|buildserver}} | ||
| Line 37: | Line 54: | ||
|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:<br/> | |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:<br/> | ||
<br/> | <br/> | ||
https://sourceforge.net/projects/flightgear/files/unstable/ | https://sourceforge.net/projects/flightgear/files/unstable/ | ||
<br/> | <br/> | ||
(And hence, all the SF mirrors)<br/> | (And hence, all the SF mirrors)<br/> | ||