Hi all, I've been working on setting up an instance of buildbot for the eventual replacement of patchbot. It doesn't have all the features of patchbot yet, so for the moment being it is an addition, not a replace.
If you would like to try it out, I have setup a sandbox trac server at http://trac-sandbox.sagedev.org to play with. How to use: 1. Push and pull to [email protected] like you would the normal trac server 2. Put your branch on some ticket, and mark it as needs review or positive review. This will trigger the buildbot to test your branch. 3. You should see on the ticket (right below the ticket number) the status of the buildbot. Once the build has started, this should provide a link to the build. Things to know (caveats): 1. The sandbox is based on a snapshot of the trac server from a few weeks ago, nothing that has happened in the meantime will be seen on the snapshot. 2. The branch links will likely be broken -- this is a side affect of not setting up a second cgit instance (and will not be broken once this stuff migrates back to the real trac instance). 3. Anything you put on the sandbox should be considered lost -- it will not be migrated back over to the real trac server. 4. Right now there is a single buildslave, so only one ticket will be tested at a time. You can see the overall status of the buildbot at http://build.sagedev.org/waterfall. 5. Changes that require new upstream tarballs won't currently work (unless your tarball is already in a standard place) -- adding this is on the TODO list. ----- I have also done a bit of refactoring with some of the other trac plugin code, so please make sure that I haven't broken your favorite feature. ----- Finally, for those of you who use the xmlrpc interface (all 3 of you), I've added the following new functions: - str merger.getMerge(int) -- takes a ticket number and returns the merge that trac uses both for the diff display, and for the buildbot - list buildbot.get_build(int) -- takes a ticket number and returns a 3-tuple [builder_name, build_number, status], where status is -1 for in progress, and is the buildbot result code for completed builds (0 for success, 1 for warnings, 2 for failures, etc...) -- Andrew -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
