Le 06/05/2010 23:53, Brad Allen a écrit :
Hello,
I'm looking for case studies or other examples of management of a development/test/build/QA/release process involving lots of Python packages with dependencies.
Our context is a research teams working togeteher and integrating different packages both in Python and C, C++ and Fortran. We use buildbot for the continuous integration. All the stages (build, installation, test, QA upload) are done using setuptools. Each package is - built (C, C++ and Fortran) using scons integrated with setuptools. - install, test, QA - egg are cretaed with the version (X.Y.Z) and svn revision. It depends on the exact revision number of each its dependencies for binary compatibility. Finally the eggs are upload on a central repository. It is quite inflexible if you use Python packages, but it is needed when you use binary packages with cross dependencies. cheers Christophe
At work currently, we use Hudson for running our tests, and are using it to produce eggs, sdists, and PIP requirements files. It's shaping up to be a nice way to build our packages, but it's about to get a lot bigger with a lot more packages and complex dependencies. We're working on defining processes for our developers and testers, and we're inventing as we go.
I have a good idea where we need to go with this, but our management wants to hear how others in the community handle this kind of challenge with releasing multiple dependent packages together, especially in light of workflows made possible by DVCS. (We're using Git)
Does anyone have any stories to tell on this front? _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Christophe Pradal INRIA/CIRAD project-team Virtual Plants UMR DAP - Développement et Amélioration des Plantes TA A96/02, CIRAD, Avenue Agropolis 34398 MONTPELLIER CEDEX 5, France tel : (33) 4 67 61 75 63