Team Chat Logs

February 1, 2010

2010 1
Mo Tu We Th Fr Sa Su
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
<< <   > >>

[07:15:27.402921]<semslie>hi Hodgestar :)
[07:16:44.931592]<semslie>I'd like to schedule builds to run on a cron job rather than on a commit as is usual - anyone know if bitten allows this?
[07:16:58.757863]<semslie>I've found this ticket: http://bitten.edgewall.org/ticket/531
[07:17:07.652145]<semslie>but perhaps there's another solution someone knows of
[07:17:26.537181]<semslie>Is is possible for the bitten-slave to initiate the build?
[07:18:34.827286]<Hodgestar>I think the first thing is to understand how bitten works currently. Builds don't run on commits -- builds run when a slave decides to connect.
[07:18:45.538331]<Hodgestar>Usually there is only build per commit though.
[07:19:13.135683]<Hodgestar>So the real question is how to allow multiple builds per commit (if that is what you want).
[07:20:31.177761]<Hodgestar>Do you want to purge the latest build and replace it with a new one?
[07:24:22.008135]<semslie>Hodgestar: Is it correct to say that a build gets queued up on a commit, and then run when a slave next requests the next build from the master?
[07:26:36.190914]<Hodgestar>The queueing also happens when a slave connects.
[07:27:09.461896]<Hodgestar>But the queueing only queues builds for new commits.
[07:28:07.274146]<Hodgestar>If you have multiple builds per platform some of the reporting goes wonky.
[07:36:22.038212]<semslie>ah I see
[07:36:55.200225]<semslie>so yes - I suppose it would mean allowing multiple builds for the tip