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... http://bazaar.launchpad.net/~linaro-validation/lava-manifest/trunk/view/head...
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
On Fri, Feb 01, 2013 at 03:22:42PM +1300, Michael Hudson-Doyle wrote:
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... http://bazaar.launchpad.net/~linaro-validation/lava-manifest/trunk/view/head...
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!
We don't need to to post-release bumps, but we still need to manage the version numbers, right? Or are we stablishing that the bzr revision is the version number now?
On 02/01/2013 06:48 AM, Antonio Terceiro wrote:
We don't need to to post-release bumps, but we still need to manage the version numbers, right? Or are we stablishing that the bzr revision is the version number now?
This is an interesting question. We still need version numbers for all non-server items. Additionally - we have things like:
http://validation.linaro.org/lava-server/version/
which are handy. Personally, I'd like to get to a "managed" version:
http://lists.linaro.org/pipermail/linaro-validation/2013-January/001587.html
However, I'm less than 50% confident that patch would be welcomed upstream.
I guess if we consolidate our server projects then it would be easy to manage this in one file with that change and we wouldn't need versiontools for the server component.
Antonio Terceiro antonio.terceiro@linaro.org writes:
On Fri, Feb 01, 2013 at 03:22:42PM +1300, Michael Hudson-Doyle wrote:
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... http://bazaar.launchpad.net/~linaro-validation/lava-manifest/trunk/view/head...
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!
We don't need to to post-release bumps, but we still need to manage the version numbers, right? Or are we stablishing that the bzr revision is the version number now?
Good questions. I guess I'd say we should still do releases in the same way (post release bumps and all until/unless Andy fixes that bit) when we upload to pypi, but that we'll upload to pypi way less frequently (like maybe monthly?).
Cheers, mwh
On 01/31/2013 08:22 PM, Michael Hudson-Doyle wrote:
Hi gang,
I've just deployed a long-awaited change: we can (and do) now deploy components such as lava-dispatcher from bzr branches.
The last time I was this happy about LAVA was when we switched to buildout. Thank you!
linaro-validation@lists.linaro.org
-
Andy Doan -
Antonio Terceiro -
Michael Hudson-Doyle -
Michael Hudson-Doyle