Opened 20 years ago

Closed 13 years ago

#58 closed task (fixed)

Migrate from tinderbox to buildbot

Reported by: Olly Betts Owned by: Richard Boulton
Priority: low Milestone:
Component: Buildbot Version: other
Severity: minor Keywords:
Cc: Blocked By:
Blocking: Operating System: other

Description (last modified by Richard Boulton)

Tinderbox isn't cleanly configurable in the way we want, so I've had to hack it around a lot. Buildbot looks a much better bet, as it's designed to allow modification by subclassing.

Change History (15)

comment:1 by Olly Betts, 20 years ago

Blocking: 51 added

comment:2 by Olly Betts, 20 years ago

Blocking: 54 added

comment:3 by Olly Betts, 20 years ago

Status: newassigned

comment:4 by Olly Betts, 18 years ago

Component: otherBackend-Flint
Severity: normalenhancement

comment:5 by Olly Betts, 18 years ago

Component: Backend-FlintWebsite
Priority: highlow

comment:6 by Olly Betts, 18 years ago

Owner: changed from Olly Betts to Not currently assigned
Status: assignednew

I can't see myself finding time to work on this in the forseeable future...

comment:7 by Richard Boulton, 17 years ago

Status: newassigned

I've set up a buildbot on atreus. It's currently only testing unix - I've got a windows MSVC build half configured, but it's proving very hard to get it working.

The web interface is not currently publically visible, but the IRC bot is sitting in #xapian-devel on irc.freenode.net.

comment:8 by Richard Boulton, 17 years ago

Owner: changed from Not currently assigned to Richard Boulton
Status: assignednew

The buildbot now performs builds of tarballs (whenever new ones appear) as well as builds tracking SVN. I plan to add the following in the near future (ie, within the next few weeks), not necessarily in this order:

1) Add windows builds from tarballs. I think the easiest way to do this will be to write a script to live on the windows machine which manages the whole build - bypassing much on buildbot's machinery which seems to get in the way. 2) Implement build-over-ssh, with the client running on atreus, but transferring files to a remove machine and running the build commands using ssh. 3) Add builds with --enable-debug and --enable-log (and both).

comment:9 by Richard Boulton, 17 years ago

Operating System: other
Status: newassigned

comment:11 by Richard Boulton, 17 years ago

Component: WebsiteBuildbot
Description: modified (diff)

comment:12 by Richard Boulton, 17 years ago

Blocking: 54 removed

comment:13 by Olly Betts, 16 years ago

HP have shut down their testdrive, which is sad but means that we don't need to worry about having to access boxes by ftp and telnet any longer at least!

How are we doing on the 3 points in comment:8?

1) I see "xapian tar win32" in buildbot, but it hasn't built in the recent past. Is this done?

2) "build-over-ssh" is what's needed for the remaining boxes I have access to. Did you get around to doing this?

3) This is done now.

comment:14 by Olly Betts, 16 years ago

Summary: Convert from tinderbox to buildbotMigrate from tinderbox to buildbot
Type: enhancementtask

Ticket #249 suggests adding a build with GLIBCXX_DEBUG, which seems a good idea.

comment:15 by Olly Betts, 16 years ago

Blocking: 51 removed

(In #51) On further reflection, I feel that passing "make distcheck" on one platform is probably good enough. If people aren't comfortable with the possibility of portability issues, then I don't think they'll be comfortable with SVN snapshots anyway. Also, we have more regular release schedule now than we did when this idea first came up, and will have development releases from a 1.1 branch fairly soon.

So I'm going to just close this bug.

comment:16 by Olly Betts, 13 years ago

Resolution: fixed
Status: assignedclosed

So the only point left here seems to be implementing some stuff to allow the buildbot slave to run on atreus and transfer files with scp and execute commands using ssh, so that we can run builds on machines where installing everything needed to run a slave isn't really an option, or where firewalling gets in the way.

I've created #582 for that issue, and am closing this ticket now.

Note: See TracTickets for help on using tickets.