[TIP] continuous integration - what are you using?
laurent.ploix at gmail.com
Thu Sep 3 02:08:44 PDT 2009
We use BuildBot and QuickBuild.
Your choice should really depend on your (technical and functional)
a) You may have to connect to a specific code repository, and not every CI
tools comes with a good integration for exotic ones.
b) You may want to run plain unit tests... or much more complicated ones. We
run tests that last for dozens of hours... and there are specific issues to
deal with (such as timeouts, for instance)
c) You may want to customize your test steps a lot (running exotic tests,
storing test results in a DB, etc.). In this case you want to have a tool
that you feel comfortable extending.
d) You may want to have complicated workflows (such as running performance
tests only of the unit tests pass on all platforms, synchronizing tests on
different platforms, etc). In this case, you want a CI tool with advanced
workflow capabilities... or you want to integrate the CI tools *within *a
workflow engine (we use a BPM for that).
As far as I know, there is not tool that covers everything anyway.
2009/8/28 C. Titus Brown <ctb at msu.edu>
> Hi all,
> I think I'm going to do a comparison of CI tools soon, and I wanted to
> know what people are using in their Python projects. So far I'm
> planning on looking at these three:
> plus pony-build as a different (and differently problematic, I'm afraid)
> way of doing things.
> I don't get the sense that bitten is used terribly much, but I'm willing
> to change my mind if I get many howls of protest.
> Anything else that people think I should look at?
> C. Titus Brown, ctb at msu.edu
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python