Buildbot?
Moderator: Moderators
Re: Buildbot?
http://www.osdev.org/phpBB2/viewtopic.php?t=12074
IMHO the buildbot should be compiling with debug symbols and provide them as a separate download (on my box it's 12MB 7zipped.)
IMHO the buildbot should be compiling with debug symbols and provide them as a separate download (on my box it's 12MB 7zipped.)
Re: Buildbot?
Something like this http://planetspring.free.fr/spring/debu ... g_R5845.7z ?
Re: Buildbot?
BuildServ is now using mingw32 4.2.1-sjlj to cross compile Spring (since release R5889). Debug symbols are much bigger now however :/
I moved all files generated previously with mingw32 3.4.5 into http://planetspring.free.fr/spring_old/ .
I moved all files generated previously with mingw32 3.4.5 into http://planetspring.free.fr/spring_old/ .
Re: Buildbot?
I just added an optionnal revision parameter for command "!rebuild":
!rebuild [<revision>]
It makes BuildServ build a specific revision instead of the latest available on SVN repository.
!rebuild [<revision>]
It makes BuildServ build a specific revision instead of the latest available on SVN repository.
Re: Buildbot?
the real buildbot is finally making installers (+ debugging symbols) again:
http://spring.clan-sy.com/dl/buildbot
http://spring.clan-sy.com/dl/buildbot
Re: Buildbot?
Nice to see the buildbot builds back online.
Time has come to stop buildserv uploads
Time has come to stop buildserv uploads

Re: Buildbot?
Meh, I am just glad that you provided this service to the community of developers and game designers during this period. Being without SVN builds really hampers development for a lot of people trying to keep abreast of what's going on with Spring, and I really appreciated the effort to keep such resources available during the outage caused by unknown-files going down.
Re: Buildbot?
Um, I hate to whine and complain about the mighty Buildbot returning from its coma, but it's 4 revs behind Bibim, has it failed to compile?
Re: Buildbot?
Well, we thought it had returned, but then Fnordia's server ran out of space so we need him to install a new HD.
Re: Buildbot?
Doh
Ok, then I'll just, erm, hope that Bibim's host works still...

Ok, then I'll just, erm, hope that Bibim's host works still...
Re: Buildbot?
Actually I already had the SVN Spring build system for my own needs. I also already had the Spring bot engine for my Linux AutoHost. All I did was linking this together and adding auto-uploads with a few lines of PerlArgh wrote:Meh, I am just glad that you provided this service to the community of developers and game designers during this period. Being without SVN builds really hampers development for a lot of people trying to keep abreast of what's going on with Spring, and I really appreciated the effort to keep such resources available during the outage caused by unknown-files going down.

I was just reactivating BuildServ uploads while you were typing this messageArgh wrote:Ok, then I'll just, erm, hope that Bibim's host works still...

I will deactivate uploads again when the new HD is installed to avoid confusing ppl with multiple SVN builds download locations. But I think I will keep the bot running because it's still useful for me for generating Windows binaries easily and for autoupdating my Linux AutoHost.
Re: Buildbot?
I've changed the rebuild command syntax:
All parameters are optional and can be put in any order:
_ sys: system for which binaries must be built (default value: "windows")
_ rev: revision to build (default value: "HEAD" => latest commit)
_ upload: tells if binaries must be uploaded (default value: "yes" if sys="windows" and branch/tag are undefined, "no" else)
_ branch: branch to build (default value: undefined => trunk)
_ tag: tag to build (default value: undefined => trunk)
I kept backward compatibility, so:
"!rebuild linux" is handled as "!rebuild sys=linux"
"!rebuild 1234" is handled as "!rebuild rev=1234"
Compiler version depends on target system:
_ windows: i586-mingw32msvc-g++ (GCC) 4.2.1-sjlj (mingw32-2)
_ linux: g++ (Debian 4.3.1-2) 4.3.1
_ windows64: x86_64-pc-mingw32-g++ (GCC) 4.4.0 20080806 (experimental)
Code: Select all
!rebuild [sys=windows|windows64|linux] [rev=<revision>|HEAD] [upload=yes|no] [branch=<branchName>] [tag=<tagName>]
_ sys: system for which binaries must be built (default value: "windows")
_ rev: revision to build (default value: "HEAD" => latest commit)
_ upload: tells if binaries must be uploaded (default value: "yes" if sys="windows" and branch/tag are undefined, "no" else)
_ branch: branch to build (default value: undefined => trunk)
_ tag: tag to build (default value: undefined => trunk)
I kept backward compatibility, so:
"!rebuild linux" is handled as "!rebuild sys=linux"
"!rebuild 1234" is handled as "!rebuild rev=1234"
Compiler version depends on target system:
_ windows: i586-mingw32msvc-g++ (GCC) 4.2.1-sjlj (mingw32-2)
_ linux: g++ (Debian 4.3.1-2) 4.3.1
_ windows64: x86_64-pc-mingw32-g++ (GCC) 4.4.0 20080806 (experimental)
Re: Buildbot?
stacktrace translator command added:
It translates the stack trace pointed by <URL>, and uploads the result to http://planetspring.free.fr/spring/stacktrace (<URL> can also be a pastebin link). The default behavior is to use the latest debug symbols for trunk (rev=LAST). This behavior can be changed by using "rev", "branch" or "tag" optional parameters (as for "rebuild" command).
Code: Select all
!translate file=<URL> [rev=<revision>|LAST] [branch=<branch>] [tag=<tag>]
Re: Buildbot?
you've won one free internets with this one. great stuff.
Re: Buildbot?
yes, really nice. 
thank you!

thank you!
Re: Buildbot?
2 new commands added for BuildServ build profiles management.
A build profile is a set of configure flags used by BuildServ during build process. The profile named "default" is used by default when no profile is given for !rebuild and !translate commands.
You can create your own build profile with the "defineProfile" command:It (re)defines the build profile named <profileName>, with its associated configure flags (<configFlag>=<value> ...). New build profiles are based on the "default" one, so there is no need to declare a config flag if it has the same value as in the default build profile.
You can list existing build profiles with the "listProfiles" command. It lists BuildServ build profiles with their associated configure flags.
So now, to build Spring with GML, you just have to enter "!rebuild profile=GML" (uploaded files will be prefixed with "[<profileName>]", so each build profile is totally independent).
A build profile is a set of configure flags used by BuildServ during build process. The profile named "default" is used by default when no profile is given for !rebuild and !translate commands.
You can create your own build profile with the "defineProfile" command:
Code: Select all
Syntax:
!defineProfile <profileName> <configFlag>=<value> [<configFlag>=<value> [...]]
Code: Select all
Exemple:
!defineProfile GML gml=true
Code: Select all
Exemple:
!listProfiles
* BuildServ * Available build profiles:
* BuildServ * GML: gml=true debug=yes optimize=yes debugdefines=no
* BuildServ * default: gml=false debug=yes optimize=yes debugdefines=no