Hi gang, I've just deployed a long-awaited change: we can (and do) now deploy components such as lava-dispatcher from bzr branches. If you look at the new buildout configuration files:
http://bazaar.launchpad.net/~linaro-validation/lava-manifest/trunk/view/head:/buildout.cfg#L127 http://bazaar.launchpad.net/~linaro-validation/lava-manifest/trunk/view/head:/buildout-production.cfg#L37 I hope it's reasonably self-explanatory what's going on: lines like lava-dispatcher = lp:lava-dispatcher in [branches] section says "satisify a requirement for the egg lava-dispatcher from the branch at lp:lava-dispatcher". Lines like lava-dispatcher = 551 in the [revisions] section -- only present in the locked-down buildout-production.cfg -- specify which revision to use. So when you want to deploy a fix to production, no need to futz with pypi and tags and post release bumps -- just push to trunk, update the revno in buildout-production.cfg and run lava-deployment-tool update! I hope this makes all of our lives a bit easier and let's us reduce the time between coding a fix and getting it to our users even more. Cheers, mwh _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
