cf-charmers team mailing list archive

[Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>]

what commands are you using to run deployer?


On Mon, May 26, 2014 at 9:55 AM, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:

> Thank you for answering
>
> This command still shows the problem:
>
> lomov:~/work/launchpad/bundle/trusty/cf-cloud-controller → bzr revno --tree
> 28
>
> I expected to get 26 as an output.
>
>
> On 26 May 2014 16:15, Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>wrote:
>
>> your methodology in the gist is flawed, log will always show the full
>> history. if you want to know the revision of the working copy use $  bzr
>> revno --tree
>>
>>
>>
>>
>>
>> On Mon, May 26, 2014 at 8:26 AM, Alexander Lomov <lomov.as@xxxxxxxxx>wrote:
>>
>>> Hello, Kapil.
>>>
>>> We've noticed that juju-deployer fetches last revisions for branches
>>> that are listed in bundle.yaml file without looking if tags are set.
>>>
>>> For instance, I want to reference to @last_good (which is set to
>>> revision 26) tag of cloud-controller charm, after I run bundle deployer
>>> command I see the latest revision inside trusty/cf-cloud-controller folder.
>>> If I understand it right it has to fetch revision 26. Changes are applied
>>> only after changing cf-cloud-controller repo manually.
>>>
>>> You can find details in this gist:
>>> https://gist.github.com/allomov/dbc9154d6d5a432eefda
>>>
>>>
>>> Thank you,
>>> Alex.
>>>
>>
>>
>