#163 (Automatic build server) – HoverRace

Ticket #163 (closed defect: fixed)

Opened 4 months ago

Last modified 6 weeks ago

Automatic build server

Reported by: ryan Owned by: ryan
Priority: major Milestone: HoverRace 1.24
Component: Build System Version: 1.23
Keywords: automatic build system Cc:
Blocking: #52 Blocked By:

Description

I've been working on this one for a little while.

CruiseControl.NET is what I've used to embark on an automatic build system. Ideally, it will wait for a few minutes after a checkin (to make sure more isn't coming), then build HoverRace. Upon failure, angry emails go out to various people, but upon success, the compiled executable is collected and put in the right places.

Binary patches for each version need to be created; then they need to be uploaded to the update server (see #52).

As it stands the CruiseControl.NET server is running at  http://ccnet.igglybob.com/ and it successfully builds HoverRace but does not do anything past that. This ticket is to keep track of progress (and if anyone has any comments).

Change History

Changed 4 months ago by ryan

  • status changed from new to assigned

Oops, that's  http://ccnet.igglybob.com/ccnet/ until I figure out Apache reverse proxy right.

Changed 6 weeks ago by ryan

  • status changed from assigned to closed
  • resolution set to fixed

This was finished a while ago actually, but I ran into other problems.

The CruiseControl.NET server now builds HoverRace, generates patches, uploads the patches to hoverrace.com/patches, uploads the built dists to hoverrace.com/dist/, and emails hoverrace-svn@… if there are build problems.

However the only outstanding issue is that updater.exe hangs for an as-of-yet unknown reason. That does not affect the fact that the build server has been successfully configured, though.

Note: See TracTickets for help on using tickets.