Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

We need a CI system #371

Closed
elad661 opened this issue Nov 21, 2013 · 5 comments
Closed

We need a CI system #371

elad661 opened this issue Nov 21, 2013 · 5 comments
Labels

Comments

@elad661
Copy link
Contributor

elad661 commented Nov 21, 2013

Now that we have tests, we need a CI system such as Jenkins or anything else that might fit, to check every commit and inform us if tests fail.

@triplem
Copy link

triplem commented Nov 23, 2013

What about buildbot? Written in python and kind of easy to adapt to own needs

@elad661
Copy link
Contributor Author

elad661 commented Nov 23, 2013

Doesn't really matter what CI system we use, as long as we actually use one.

@flyte
Copy link
Contributor

flyte commented Jan 11, 2014

I use Jenkins at work which does the job, but Travis CI might be nice as it's free for open source projects. https://travis-ci.org/

@bui
Copy link
Contributor

bui commented Jan 11, 2014

@elad661
Copy link
Contributor Author

elad661 commented May 1, 2014

I guess we have a (working) CI now, so this can be closed. We do, however, need tests for non-module features. Current tests only support modules and some (basic) stuff like web.py and tools.py that modules use.

tests for core is issue #268, but I don't think anyone is actively working on it at the moment.

@elad661 elad661 closed this as completed May 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants