Page 1 of 1

On the bleeding edge: Nightly builds - how to get them

Posted: Fri Mar 10, 2006 11:38 pm
by winston
Oolite on Linux now has a nightly build, and it now has a shiny new server to do it on (as of 2007-12-03). Nightly builds are done whenever there is a new SVN revision (otherwise it doesn't bother), and occur at 01:00 GMT.

NEW - Status page can be found here:
http://www.alioth.net/oolite/status.html

The nightly build provides a way to be on the bleeding edge without needing the development kit (all the dev libraries etc.) Nightly builds currnently can ONLY be downloaded with rsync.

How to get it:

Go into the top level Oolite directory for your installation. This will be one of the following locations -
If you used the Autopackage:
Installed as root - /usr/lib/Oolite
Installed as a normal user - $HOME/.local/lib/Oolite

If you used the tarball:
Installed as root - /usr/local/Oolite
Installed as a normal user: $HOME/Oolite

Then run the following command - note the trailing dot (which might be hard to see if you are using a very small font with your web browser):

Code: Select all

rsync -rl rsync://rsync.alioth.net/oolite/nightly/Linux-x86/* .
...and you will be brought up to whatever the last successful nightly build was.
There are some useful files that appear in is directory:

release.txt - The version number of the game (for nightlies - it's ooliteversion-minornumber-svnrevision, for example 1.64-dev1-310)

buildinfo.txt - Build info. IMPORTANT - Please include the contents of this file when making a bug report! Just 'cat buildinfo.txt' and paste the result. (Future versions of the oolite startup script will show this information when the game crashes).

changelog.txt - The change log, as extracted from Subversion

Also, I'm hoping to shortly have the nightly build also update a small web page which will show the status of the build, when it was last built etc.

Posted: Sun Apr 02, 2006 1:59 am
by Galileo
The nightly build has stopped working for me, it's stopped at r388. Is this just a problem on my end?

Posted: Sun Apr 02, 2006 7:58 am
by winston
No, the build was broken. See the oolite-pc forum.

Posted: Sun Apr 02, 2006 5:13 pm
by Ponder
Why is info about the Linux nightly build in the PC (windows) forum?

I had a look and can't find it.

Can you point it out please?

Posted: Sun Apr 02, 2006 5:24 pm
by winston
It was because the discussion of the changes in question happened to be there (the getting rid of AppKit thread).

Posted: Mon Apr 03, 2006 12:29 pm
by Ponder
Thanks, found the thread which states it's fixed but it's till not updating.

release.txt still tells me I'm using 1.62-5

Forget it, my bad. Remembered the last dot but missed out the slash before the asterisk :oops:

Posted: Mon Jul 31, 2006 11:30 am
by randall
In the lastest nightly (release.txt says 1.65-678) no messages show up on the screen, e.g. hyperspacing gives you an audio count-down, but it doesn't show anything on the screen.

Just wanted to tell in case you hadn't noticed :D

Posted: Sun Aug 27, 2006 7:43 pm
by ArkanoiD
randall wrote:In the lastest nightly (release.txt says 1.65-678) no messages show up on the screen, e.g. hyperspacing gives you an audio count-down, but it doesn't show anything on the screen.

Just wanted to tell in case you hadn't noticed :D
The problem is still there for 703 and no newer builds for more than 2 weeks!

Posted: Mon Aug 28, 2006 8:11 am
by winston
It's borked for the time being, new shader stuff doesn't compile on Debian due to older libraries. Unfortunately I'm going to have to make a custom build env to make it work properly.

Posted: Tue Sep 05, 2006 6:24 pm
by ArkanoiD
winston wrote:It's borked for the time being, new shader stuff doesn't compile on Debian due to older libraries. Unfortunately I'm going to have to make a custom build env to make it work properly.
Still there - more than a month stuck with the buggy version :-(

Posted: Thu Sep 07, 2006 8:52 am
by winston
Sorry, too many other projects and a distinct lack of tuits has prevented me from looking at upgrading the build environment on vexed3 (which will be non-trivial since I now have to replace all the Debian stuff with custom compiled stuff. Either that or leave my workstation turned on all the time to do the builds, which isn't really an option either since it makes quite a measurable impact on my electricity bill).

I'm also away all of next week, so don't hold your breath. Sorry!

Posted: Thu Sep 21, 2006 9:11 am
by ArkanoiD
winston wrote:Sorry, too many other projects and a distinct lack of tuits has prevented me from looking at upgrading the build environment on vexed3 (which will be non-trivial since I now have to replace all the Debian stuff with custom compiled stuff. Either that or leave my workstation turned on all the time to do the builds, which isn't really an option either since it makes quite a measurable impact on my electricity bill).

I'm also away all of next week, so don't hold your breath. Sorry!
Any news? ;-)

Posted: Mon Dec 03, 2007 4:59 pm
by winston
Nightly builds are now up and running on a shiny new server.
Build status (last successful build, stdout messages, stderr messages) can be obtained from:

http://www.alioth.net/oolite/status.html

Although the build is on a new server, the rsync repository has not moved.

Getting Nightly Build

Posted: Fri Jan 04, 2008 5:16 pm
by davcefai
If you want feedback from rsync, rather than a blank screen, you can use this:

Code: Select all

rsync -rlv --progress rsync://rsync.alioth.net/oolite/nightly/Linux-x86/* . 
I have added the -v (verbose) and --progress options to the invocation.

Posted: Mon Sep 21, 2009 6:51 pm
by Getafix
A Nightly Build Status service is available at:
http://terrastorage.ath.cx/oolite/status.html
as an alternative to the relevant alioth.net service.

Notes:
  • The source is updated and build daily (I mean nightly...) at 00:00 06:00 UTC.
  • Following to a_c's suggestion 8) , a download link for "bleeding edge" package is added.
  • The package is installed in its own location so as not to interfere with oolite releases setup.
    However, some folders (e.g. .Oolite, oolite-saves, Cache) may be commonly used between
    different installations. Therefore, when a released oolite is installed, use "bleeding edge" oolite with caution.
    The "bleeding-edge" oolite is run by typing "oolite-trunk" in a terminal window or by the related Games/oolite-trunk desktop menu.
  • The oolite-trunk displays the version.revision watermark.
  • Once the "bleeding edge" package is installed, it is not necessary to download full
    setup again. Just run 'oolite-trunk-update' (or "sudo oolite-trunk-update" if the package was
    installed as root) from a terminal window and only the updates will be downloaded from the alternative server.
Cheers.