On 2010-11-29 13:59, David Kirkby wrote: > The addition of the buildbot to Sage should be a good thing. But it > seems to get very little use. I know the Wireshark projects runs their > buildbots 24/7. Any failures are emailed to the developers, along with > a list of who has committed source since the last successful build. I > appreciate that its not practical to do this on all machines (I for > one would not appreciate if 'hawk' was constantly running Sage tests.. > But its 10 days since the buildbot was last run, yet in that time, > there has clearly been tickets committed.
Let me answer this from a release manager point-of-view. Currently, the buildbot is essentially only used to test new Sage (alpha) releases and I must say it is extremely for that. I don't know that much about the buildbot, but I believe it is not easy to allow for testing of different tarballs (like, user 1 wants to test tarball X and user 2 wants to test tarball Y). Right now, the path is actually hardcoded and must be changed for each release. It would be good for me to test pre-releases more often while they are prepared. I almost continuously build new Sage distributions, testing various tickets. For example right now there is a sage-4.6.1.alpha3 tarball which will of course not be the final one. I proposed the following to Mitesh Patel: to have the hardcoded path point to a location which is easily changed, there could be a symbolic link /home/buildbot pointing to some sage release. This would still not allow users to easily test their tarballs, but it would certainly help the release manager to test tickets. Jeroen. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
