Comment #24 on issue 1117 by vlada.pe...@gmail.com: Setup buildbot (again)
http://code.google.com/p/sympy/issues/detail?id=1117
I've posted some thoughts on this on my blog, read it here:
http://vperic.blogspot.com/2011/05/continuous-integration-and-sympy.html
In short, I think using Tox and Jenkins is a preferable solution. Tox
itself is a very powerful tool which will be a big help with the
development process, and the Jenkins integration on top is just a bonus. As
mentioned in the blog post, a small problem is the lack of "try" support -
Ondrej, I'm positive the code in sympy-bot can be adapted to be ran from
Jenkins, will you be able to help me with this?
And of course, we need to have a server to run Jenkins on. How should we go
about this?
Finally, I think introducing Tox to the development process right away is a
good idea. I'll write up a wiki page about it (it's really very simple) and
we can see how it'll work in practice.
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To post to this group, send email to sympy-issues@googlegroups.com.
To unsubscribe from this group, send email to
sympy-issues+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sympy-issues?hl=en.
