Re: [Openerp-community] Deployment best practices

2014-05-24 Thread Mignon, Laurent
Hello all, On Sat, May 24, 2014 at 8:14 PM, Raphael Valyi wrote: > > An alternative could be that when the recipe is "converged" to the desired > state, it could produce some kind of buildout.lock file where exact > revision converged would be kept under revision control. > Several packages ma

Re: [Openerp-community] Deployment best practices

2014-05-24 Thread Lorenzo Battistini
Il giorno 24/mag/2014 20:14, "Raphael Valyi" ha scritto: > > What is the idea? never say last:1 / HEAD and always specify revisions to deploy? That sounds possible, but is it ideal? > We do that way ___ Mailing list: https://launchpad.net/~openerp-commu

Re: [Openerp-community] Deployment best practices

2014-05-24 Thread Ovnicraft
On Sat, May 24, 2014 at 1:14 PM, Raphael Valyi wrote: > hello all, > > a deployment issue I have with the Anybox recipe is that if you target > HEAD or say last:1 on bzr branches, the recipe will try to grab the last > available revisions. But it won't freeze anywhere the versions being > actuall

Re: [Openerp-community] Deployment best practices

2014-05-24 Thread Raphael Valyi
hello all, a deployment issue I have with the Anybox recipe is that if you target HEAD or say last:1 on bzr branches, the recipe will try to grab the last available revisions. But it won't freeze anywhere the versions being actually deployed. So if in an other environment you want to replicate the