On 12/20/2013 07:09 AM, Vincent Ladeuil wrote:
7 commands to issue manually ? No tests ?
Are there ways to have automated tests for that so we*know* setting up the env is automated ?
We have lots of unit-testing and given where we are - i think that's sufficient for dev-environments.
And people wonder why I dislike pip and its fallouts ? (This is just the tip of the iceberg we're hitting here, pip won't work in prodstack as is).
I don't like pip, but that's orthogonal to this. If you move stuff to a PPA you wind up with three new steps (add-apt-repo, apt-get-update, apt-get-install) and only remove steps. I gladly welcome anyone to package our dependencies.
Also note: 3 of those 7 steps were required because psiva was trying to use postgres in his dev-environment instead of sqlite3.
I think the real thing you've stumbled on is that it would be nice to have a script like "dev-env.sh" that will setup any or all of our components for local-development.
-- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
