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

Continuous integration #26

Open
Ffisegydd opened this issue Nov 26, 2014 · 6 comments
Open

Continuous integration #26

Ffisegydd opened this issue Nov 26, 2014 · 6 comments
Labels

Comments

@Ffisegydd
Copy link
Member

When sopython-site gets some unittests, will you have some kind of CI set up? If so, did you have any opinion on what to use? Might as well use the same as for Nidaba. IntrepidBrit suggested http://jenkins-ci.org/

@joncle
Copy link
Contributor

joncle commented Nov 26, 2014

It's "continuous" integration :)

I'd go for https://travis-ci.org

@Ffisegydd Ffisegydd changed the title Constant integration Continuous integration Nov 26, 2014
@Ffisegydd
Copy link
Member Author

I've used travis myself in the past. There's also https://www.jetbrains.com/teamcity/ possibly (<3 JetBrains :P)

And I was just testing you with the title, well done, you won.

@vaultah
Copy link
Member

vaultah commented Nov 26, 2014

http://vexor.io is said to be good

@vaultah
Copy link
Member

vaultah commented Nov 26, 2014

It also supports Py3k

@OldTinfoil
Copy link

If none of us has firm views on CI server, then we should let whoever is willing maintain the CI pick their favourite flavour of CI software.

@AlexFrazer
Copy link
Member

Jenkins is pretty good. I don't think the choice is particularly significant for python because most python software seems to run well on every Ci (as it is so popular.)

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

6 participants
@AlexFrazer @OldTinfoil @joncle @Ffisegydd @vaultah and others