idvoretskyi / buildbot Goto Github PK

Otherwise the symbols files are hard to find and take up a lot of space.

And generally make it easier to decrypt user backtraces.

Building them separately, in parallel, would speed up the release process and make debugging easier.

There is a commit status api that would allow us to push the result of the test run straight into the PR itself.

This would be mainly for 3rd party PRs, we might want to whitelist PRs from rethinkdb developers so they aren't blocked from merging something that's already been reviewed.

Some recently found bugs could have been caught by running the tests under valgrind.

This looks like it could be a bug in buildbot:

http://trac.buildbot.net/ticket/2873

This has caused the delete-old-files builder to not be run.

If this happens again, the offending buildrequest can be deleted from the buildbot database with a command such as:

sqlite3 /home/buildbot/buildbot/master/state.sqlite "delete from buildrequests where buildername = 'delete-old-files' and complete=0;"

Our docs currently recommend using the lucid package on debian.

Versoin 1.15 of that package does not work on debian wheezy.

Currently, files are copied manually using rsync. rsync copies the files one at a time, which is not safe. Users of yum or apt might find the respective repository in an inconsistent state.

There should be wrapper around rsync that updates the server atomically, perhaps by using the --partial-dir, --delay-updates or --link-dir option.

The APT repo is currently built by patching the files generated by freight.