cf-charmers team mailing list archive

[Cory Johns <cory.johns@xxxxxxxxxxxxx>]

Alex,

My apologies.  That was supposed to go to a feature branch, but was applied
to a lightweight checkout by mistake and so automatically pushed itself.  I
was told, though, that it wouldn't be a problem, since the bundle was
tagged to specific revisions of the charms, but then the tagging was
removed in trunk after that, which caused it to become an issue.

So, I've pushed a revert commit to fix cf-dea/trunk, and the feature
branches are up for review separately and can be all merged together when
ready, as they were intended.


On Wed, May 14, 2014 at 12:22 PM, Prismakov Alexander <
alexander.prismakov@xxxxxxxxxxx> wrote:

>  Hi Cory,
>
>  After 32 revision of cf-dea we have broken upstart jobs (e.g. cf-warden
> actually contains dir-server job)
> Please take look here -
> http://bazaar.launchpad.net/~cf-charmers/charms/trusty/cf-dea/trunk/view/head:/hooks/hooks.py#L48<http://bazaar.launchpad.net/~cf-charmers/charms/trusty/cf-dea/trunk/view/head:/hooks/hooks.py#L52>
>
>  Guys, please be more careful with pushing code to trunk. Code need to be
> checked by integration tests (at least manually)
> before applying to trunk.
>
>  Now we need to redeploy CF, reconfigure and rerun MySQL broker etc.
>
>  -Alex Prismakov
>
>
>
>