is the buildbot broken?
-
lav_coyote25
- Professional

- Posts: 3434
- Joined: 08 Aug 2006, 23:18
is the buildbot broken?
the last build is from the 26 of june 2011 and it is now 28 june 2011.... whats the deal???
-
cybersphinx
- Inactive

- Posts: 1695
- Joined: 01 Sep 2006, 19:17
Re: is the buildbot broken?
No commits since then? I think Safety0ff made it build only after new commits, not sure if that includes after every commit or more than once a day.
We want information... information... information.
-
Safety0ff
- Trained

- Posts: 397
- Joined: 18 Jul 2009, 23:23
Re: is the buildbot broken?
Currently it is set up to only make builds if there are new commits (so as to not lead people on to believe that all newer nightlies contain code/assets that aren't in a previous build).
Currently commit poller polls every hour, the build scheduler checks for new commits every 15 minutes (and it seems like it runs before the commit poller). So this translates into a new build occurring between 15m to 1h15m after a new commit.
The benefits are that devs are notified more quickly if they hosed the build set up and people don't download builds which are identical to the ones they already possess.
Currently commit poller polls every hour, the build scheduler checks for new commits every 15 minutes (and it seems like it runs before the commit poller). So this translates into a new build occurring between 15m to 1h15m after a new commit.
The benefits are that devs are notified more quickly if they hosed the build set up and people don't download builds which are identical to the ones they already possess.
-
lav_coyote25
- Professional

- Posts: 3434
- Joined: 08 Aug 2006, 23:18
Re: is the buildbot broken?
ok, thanks, now i know - i wont complain ( well not too much...Safety0ff wrote:Currently it is set up to only make builds if there are new commits (so as to not lead people on to believe that all newer nightlies contain code/assets that aren't in a previous build).
Currently commit poller polls every hour, the build scheduler checks for new commits every 15 minutes (and it seems like it runs before the commit poller). So this translates into a new build occurring between 15m to 1h15m after a new commit.
The benefits are that devs are notified more quickly if they hosed the build set up and people don't download builds which are identical to the ones they already possess.