Re: [Numpy-discussion] Buildbot status
On Sun, Jul 8, 2012 at 3:44 PM, Chris Ball s0454...@sms.ed.ac.uk wrote: I'm happy to help connect slaves to the EC2 buildbot if someone sends connection details to me. Thanks very much, Chris. Matthew gave us access to the NiPy build slaves, so catch me online then we can hook those up. Another thing to consider is where to send test results. Travis-CI already comments on pull requests, which is great; the other solutions could be set up to email a list (or even the individuals potentially responsible for causing test failures). If we notify the individuals, for now, that's fine. Others can keep track by looking at the buildbot homepage. Stéfan ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Buildbot status
Stéfan van der Walt stefan at sun.ac.za writes: ... I'd like to find out what the current status of continuous integration is for numpy. I'm aware of: a) http://buildbot.scipy.org -- used by Ralf for testing releases? b) http://travis-ci.org -- connected via GitHub c) http://184.73.247.160:8111 -- dedicated Amazon EC2 with TeamCity d) http://build.pydata.org:8111/ -- dedicated Rackspace instance with TeamCity e) https://jenkins.shiningpanda.com/numpy/ -- python 2.4 on Debian There's also: f) https://jenkins.shiningpanda.com/scipy/ -- python 2.4, 2.5, 2.6, 2.7 on Debian 6 Could easily add: Windows 7 slave, and various other versions of python (3, pypy, etc.). Could also produce graphical test and coverage reports. g) buildbot on the EC2 Currently only has one old, temporary linux test slave. Should work with any available platform and python versions, but - in contrast to shiningpanda - each new addition is a machine (or VM) that someone has to volunteer and look after. Volunteer slaves would require tox and virtualenv (in addition to numpy's requirements). I propose that we following a simple migration path for now: move the current buildbot onto the EC2 instance, redirect buildbot.scipy.org, and then connect the nipy build slaves. This should require minimal effort, but provide us with fairly wide coverage until you can invest more time in Jenkins etc. I'm happy to help connect slaves to the EC2 buildbot if someone sends connection details to me. Another thing to consider is where to send test results. Travis-CI already comments on pull requests, which is great; the other solutions could be set up to email a list (or even the individuals potentially responsible for causing test failures). Chris ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Buildbot status
On Thu, Jul 5, 2012 at 4:36 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote: So feel free to go ahead with what you think is the best and I will join you in a few days. I propose that we following a simple migration path for now: move the current buildbot onto the EC2 instance, redirect buildbot.scipy.org, and then connect the nipy build slaves. This should require minimal effort, but provide us with fairly wide coverage until you can invest more time in Jenkins etc. Stéfan ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Buildbot status
On Sat, Jul 7, 2012 at 2:01 PM, Stéfan van der Walt ste...@sun.ac.za wrote: On Thu, Jul 5, 2012 at 4:36 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote: So feel free to go ahead with what you think is the best and I will join you in a few days. I propose that we following a simple migration path for now: move the current buildbot onto the EC2 instance, redirect buildbot.scipy.org, and then connect the nipy build slaves. This should require minimal effort, but provide us with fairly wide coverage until you can invest more time in Jenkins etc. I agree. Ondrej ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Buildbot status
Hi Stefan, On Tue, Jul 3, 2012 at 1:59 PM, Stéfan van der Walt ste...@sun.ac.za wrote: On Mon, Jul 2, 2012 at 6:31 PM, Travis Oliphant tra...@continuum.io wrote: Ondrej should have time to work on this full time in the coming days. That's great; having Ondrej on this full time will help a great deal. NumFocus can provide some funding needed for maintaining servers, etc, but keeping build bots active requires the efforts of multiple volunteers. If anyone has build machines to offer, please let Ondrej know so he can coordinate getting Jenkins slaves onto them and hooking them up to the master. I'd be glad if we could discuss it mainly on list, just to keep everyone in the loop. For now, I think we need to answer the two questions mentioned above: 1) What happens to the current installation on buildbot.scipy.org? 2) If we're not keeping buildbot, or if we want additional systems, which ones should we use? Jenkins? and then also 3) Which build slaves should we employ? We have the current build slaves, the nipy ones have been volunteered, and then there's the GCC build farm mentioned by Fernando. Ondrej, perhaps you can comment on what you had in mind? If we have a clear plan of action before you start off, we can all help out in putting the pieces together. The only work that I did so far was to learn Jenkins and write these Fabric files to automatically setup testing for pretty much any project, from the command line: https://github.com/certik/vagrant-jenkins If we go with EC2, then the same Fabric files can be used to provision the EC2. That way, we can keep the configuration in one public repository and people can send pull requests with improvements. And thus pretty much anyone should be able to help with the maintenance. Currently it works in a way that somebody sets it up, then becomes busy, and then the buildbots stop working. It might be too idealistic though, but if we can have most of the setup in Fabric and the rest well documented, it will be much easier for other people to help out. So feel free to go ahead with what you think is the best and I will join you in a few days. Ondrej ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Buildbot status
On Mon, Jul 2, 2012 at 6:31 PM, Travis Oliphant tra...@continuum.io wrote: Ondrej should have time to work on this full time in the coming days. That's great; having Ondrej on this full time will help a great deal. NumFocus can provide some funding needed for maintaining servers, etc, but keeping build bots active requires the efforts of multiple volunteers. If anyone has build machines to offer, please let Ondrej know so he can coordinate getting Jenkins slaves onto them and hooking them up to the master. I'd be glad if we could discuss it mainly on list, just to keep everyone in the loop. For now, I think we need to answer the two questions mentioned above: 1) What happens to the current installation on buildbot.scipy.org? 2) If we're not keeping buildbot, or if we want additional systems, which ones should we use? Jenkins? and then also 3) Which build slaves should we employ? We have the current build slaves, the nipy ones have been volunteered, and then there's the GCC build farm mentioned by Fernando. Ondrej, perhaps you can comment on what you had in mind? If we have a clear plan of action before you start off, we can all help out in putting the pieces together. Stéfan ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Buildbot status
Useful-looking: http://gcc.gnu.org/wiki/CompileFarm ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Buildbot status
Hi Stefan, On Mon, Jul 2, 2012 at 5:07 PM, Stéfan van der Walt ste...@sun.ac.za wrote: Hi all, I'd like to find out what the current status of continuous integration is for numpy. I'm aware of: a) http://buildbot.scipy.org -- used by Ralf for testing releases? b) http://travis-ci.org -- connected via GitHub c) http://184.73.247.160:8111 -- dedicated Amazon EC2 with TeamCity d) http://build.pydata.org:8111/ -- dedicated Rackspace instance with TeamCity e) https://jenkins.shiningpanda.com/numpy/ -- python 2.4 on Debian Is there interest in maintaining the buildbot setup? If so, I suggest we move (a) onto (c), and then connect in several of the NiPy buildbots [including a Raspberry Pi!] (offered by Matthew Brett). It'd be nice to have a semi-official set up, so that we don't duplicate too much effort. Yes, definitely. I will have time to work on the tests in about 2 weeks. Could you coordinate with Travis? He can make it official. Ondrej ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Buildbot status
On Mon, Jul 2, 2012 at 5:31 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote: Yes, definitely. I will have time to work on the tests in about 2 weeks. Could you coordinate with Travis? He can make it official. I'd gladly coordinate with everyone, but I'd like to do it here on the mailing list so that we're on the same page. Numerous parties have spoken about this informally, but now there are multiple efforts that I'd like to consolidate. Here are some questions we need to answer: 1) Do we keep the current buildbot.scipy.org? I suggest that we move it to the EC2 machine, if we do. Both Chris Ball and Matthew Brett has set up fairly sophisticated buildbots before, so we can leverage their knowledge. 2) Do we switch to another system, such as Jenkins? It seems as though you've investigated some of those alternatives. Did you also look at TeamCity? If anyone needs access to the EC2 machine, just let me know. Regards Stéfan ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Buildbot status
Ondrej should have time to work on this full time in the coming days. I think your list, Stefan, is as complete a list as we have. A few interns have investigated Team City and other CI systems and a combination of Jenkins and Travis CI has been suggested. NumFocus can provide some funding needed for maintaining servers, etc, but keeping build bots active requires the efforts of multiple volunteers. If anyone has build machines to offer, please let Ondrej know so he can coordinate getting Jenkins slaves onto them and hooking them up to the master. Ondrej would especially appreciate any experience with Windows nodes. Best regards, Travis -- Travis Oliphant (on a mobile) 512-826-7480 On Jul 2, 2012, at 7:18 PM, Stéfan van der Walt ste...@sun.ac.za wrote: On Mon, Jul 2, 2012 at 5:31 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote: Yes, definitely. I will have time to work on the tests in about 2 weeks. Could you coordinate with Travis? He can make it official. I'd gladly coordinate with everyone, but I'd like to do it here on the mailing list so that we're on the same page. Numerous parties have spoken about this informally, but now there are multiple efforts that I'd like to consolidate. Here are some questions we need to answer: 1) Do we keep the current buildbot.scipy.org? I suggest that we move it to the EC2 machine, if we do. Both Chris Ball and Matthew Brett has set up fairly sophisticated buildbots before, so we can leverage their knowledge. 2) Do we switch to another system, such as Jenkins? It seems as though you've investigated some of those alternatives. Did you also look at TeamCity? If anyone needs access to the EC2 machine, just let me know. Regards Stéfan ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
