Buildbot?

[zerver]

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

That's great

[Tobi]

bibim, could you update the DLLs that installer uses for SpringLobby (from springlobby.nsh) to the ones in http://www.springlobby.info/windows/dll/dlls.zip?

Or otherwise, if there's a master data of installer DLLs I forgot about, point me to it so I can update it?

[Argh]

That would be nice... also, don't forget a SpringLobby.conf file...

[bibim]

bibim, could you update the DLLs that installer uses for SpringLobby (from springlobby.nsh) to the ones in http://www.springlobby.info/windows/dll/dlls.zip?

Sure, it's done.

Or otherwise, if there's a master data of installer DLLs I forgot about, point me to it so I can update it?

You can update directly the BuildServ "external" directory by using scp/rsync with a rssh access I had initially created for LordMatt. I've sent you the connection info in pm.

[bibim]

I reverted the SDL.dll file to the previous version, because the one from your dlls.zip leads to problems with Spring binds and azerty keyboards

[Tobi]

Ah ugh, SDL strikes again

Thanks for fixing

[bibim]

Does anyone still need 0.76b1+ files on PlanetSpring ? I'm thinking about removing them to save some space and facilitate browsing.

[imbaczek]

i don't think they're needed.

[bibim]

FYI, I lost 1GB of RAM on my server a few days ago, so builds will take a little longer while the broken stick is returned to manufacturer (Corsair)

[Argh]

D'oh! Sorry to hear about that...

[AF]

Is there some way of making the system build spring OTHER than when in the lobby? Its just it would be very useful to summon up a build of the C interface branch, and I would most likely do this at work where the ports to the lobby are blocked. Setting up a spring build environment on my work computer is out fo the question, nor do I have access to svn from work anyway.

Is there another way?

[bibim]

Currently Spring lobby is the only way to trigger BuildServ builds.

P.S: Sorry for my indiscretion, but may I ask you why you are most likely to summon C interface branch builds from work, given that you don't have SVN access from work ?

[AF]

Because at work Im most likely to be using a windows machine fully kitted out with the necessary dev tools to work on my AI off a usb drive, whereas at home I'm most likely on my mac book for which I do not have a working spring setup.

Also when I'm at home if I want windows I have to goto my room and turn my desktop on where its freezing cold, or run parallels which gets messy. By this time Im already low on energy after a long day at work and have other things to sort out.

Its a matter of convenience, what would be necessary to add support for another means such as an msn bot or a web interface?

[el_matarife]

What about having Meltrax get Melbot to bridge commands between IRC and the buildbot in the lobby?

[Hoi]

Won't work if melbot adds the name of the person.

[lurker]

We're talking about having Meltrax change the code...

[AF]

I suspect IRC wont work at work though Im at home for the holidays now, by the time Ive recovered Ill be into my booked holidays so I cant find out

[bibim]

I reinstalled some RAM on the server, it should now operate at normal speed again.

Its a matter of convenience, what would be necessary to add support for another means such as an msn bot or a web interface?

Well, it shoudn't be very hard to add MSN interface since there are Perl modules that handle this protocol. It would just require implementing tasks such as synchronisation / concurrent build exclusion, redirections , flood protections etc... Web interface would be even easier but I don't want this server to become a public HTTP server.
If you have SSH access from work as I do, you can just use a SSH tunnel through your personnal computer or another server to access Spring lobby...

[hoijui]

..or ask someone else by msn, icq, oirc, phone, ...
to do it for you

[bibim]

Since Spring moved to GIT, I modified BuildServ to handle GIT repositories. And while I was on it, I took the opportunity to refactor some parts, add some features, and get rid of most of the autohost code that has nothing to do with a buildbot (BuildServ is originally based on SPADS code).

So here is an overview of what has changed lately for end-user:

• Generic VCS (Version Control System) support:
  A new optionnal "vcs" parameter has been added to !rebuild and !translate commands. Allowed values are "git" and "svn", and the default value is "svn" if the "rev" parameter is provided and numeric, "git" else.
  For the !rebuild command, the "vcs" parameter defines which repository must be fetched before rebuilding, and for the !translate command it defines which local debug symbols must be used to translate the stacktrace (like the other translate parameters, the "vcs" parameter is usually autodetected from the infolog file anyway, so that it is still possible to translate old SVN-build stacktraces without providing any parameter).
• GitHub links in translated stacktraces:
  A new optionnal "links" parameter has been added to !translate command. Allowed values are "yes" and "no", and the default value is "yes" if vcs=git, "no" else. If links=yes, the translated stacktrace is in html format and contains links to appropriate GitHub pages (source file history and source file code for the revision used to produce the crash). Here is an example of such an HTML stacktrace.
• New !history command:
  A new command !history has been added. The syntax is

  Code: Select all

  !history [rev=<revision>|HEAD] [vcs=git|svn]

  It shows the 10 last commits in reverse chronological order, starting at <revision>, or HEAD if not specified. When using GIT repository (default), it shows the branch graph and appropriate commit links to GitHub at the same time. Here is an output example.
• New !pending command:
  A new command !pending has been added, it shows what has been commited on trunk since last standard rebuild (i,e: "!rebuild" without any parameter). Here is an output example.
• Full cmake support:
  BuildServ is now able to generate the Spring installer with cmake. So now, when rebuilding for windows with "buildsys=cmake" parameter, the same files are generated and uploaded as with scons (the dedicated server is still generated with cmake only though).
• Bot status management:
  The in-game and afk/away bot status in Spring lobby gives information about current bot state. The bot is set as in-game when it's updating its local repositories, translating a stacktrace, or performing a rebuild. And it is set as afk/away when the latest uploaded revision is up to date (i,e: no commit has been performed since last "!rebuild").