Set up a continuous integration server about pyclaw HOT 6 CLOSED

Matteo provided these links:

A link to a list of open source continuous integration softwares: http://www.opensourcecontinuousintegration.com/

Other links about CI for python or python oriented: http://stackoverflow.com/questions/225598/pretty-continuous-integration-for-python

http://stackoverflow.com/questions/1719977/configure-execute-shell-scripts-in-hudon-with-python

from pyclaw.

As discussed today with David and Aron, the continuous integration server will also build the documentation and push the html files to the correct location.

Test different OS and different compilers would be very helpful to support the users.

from pyclaw.

I have Jenkins working on my laptop. It automatically pulls from Github, runs the tests, and also analyzes our code coverage and pylint violations. Now we just need to put it on a server where everybody can see the results.

from pyclaw.

Thanks David! That's great!
For the time being, if we need a desktop, we can use mine at KAUST.

Which OSs do we want to use? OS X, Linux, Windows?

On 31 December 2011 12:07, David Ketcheson <
[email protected]

wrote:

I have Jenkins working on my laptop. It automatically pulls from Github,
runs the tests, and also analyzes our code coverage and pylint violations.
Now we just need to put it on a server where everybody can see the results.

---

Reply to this email directly or view it on GitHub:
#11 (comment)

Matteo

from pyclaw.

I don't think it is worth supporting Windows -- you have to use a Unix VM
in that case anyway, so it's a bit circular. Definitely OS X and some
Linux distro.

On Sat, Dec 31, 2011 at 4:07 PM, Matteo Parsani <
[email protected]

wrote:

Thanks David! That's great!
For the time being, if we need a desktop, we can use mine at KAUST.

Which OSs do we want to use? OS X, Linux, Windows?

On 31 December 2011 12:07, David Ketcheson <
[email protected]

wrote:

I have Jenkins working on my laptop. It automatically pulls from Github,
runs the tests, and also analyzes our code coverage and pylint
violations.
Now we just need to put it on a server where everybody can see the
results.

---

Reply to this email directly or view it on GitHub:
#11 (comment)

Matteo

---

Reply to this email directly or view it on GitHub:
#11 (comment)

from pyclaw.

We're now using Travis for this. Closing.

from pyclaw.