Comment #25 on issue 1117 by [email protected]: Setup buildbot (again)
http://code.google.com/p/sympy/issues/detail?id=1117
+1 to any work that any of you do in this area. :)
I have a server, and also an AWS account if needed. The AWS is not much
free, but the linode server is pretty much ready to use. The only thing
that runs on it is the blog update, and I made it super easy to reinstall.
I will have to upgrade the linode from some old debian to the latest
ubuntu, but apart from that, it's all good. And as the planet.sympy.org
shows, the background job works super reliably so far.
If all developers agree, we can also use some money that we get from Google
for the GSoC (I think around $500) to pay for some of it. However I have no
problems to continue to pay for one linode each month (~$20/month) and I
think I can afford to pay one more if needed. So I would prefer to save the
google money for later.
Using jenkins + tox sounds awesome to me, or anything else is good too. In
general, given my experience with all this so far, we should try to
outsource as many things as possible, because otherwise somebody has to
take care of the servers and it is time consuming.
So I really like the ep.io idea, however, I just calculated that running it
fulltime will cost $250 per month (is that right?), which is too much for
me. They only charge per hour, but we will use lots of hours for tests, so
I think we'll stick with linode.
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sympy-issues?hl=en.
