You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Rajani Karuturi (JIRA)" <ji...@apache.org> on 2017/03/28 08:34:42 UTC

[jira] [Updated] (CLOUDSTACK-8310) commit to commit db upgrades and db version control

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajani Karuturi updated CLOUDSTACK-8310:
----------------------------------------
    Security:     (was: Public)

> commit to commit db upgrades and db version control
> ---------------------------------------------------
>
>                 Key: CLOUDSTACK-8310
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8310
>             Project: CloudStack
>          Issue Type: Improvement
>            Reporter: Rajani Karuturi
>              Labels: gsoc2017
>
> Cloudstack currently uses a homegrown tool to do the database upgrades. 
> The challenges with the current one being, it can only do version to version but not commit to commit upgrades.
> Due to this, when different people work on the same branch and have db changes, environment is broken untill you do fresh db deploy.
> To achieve this, we can use existing and well tested tools like liquibase, flywaydb etc. or improve on the existing one. 
> Related discussions on dev lists
> http://markmail.org/thread/aicijeu6g5mzx4sc
> http://markmail.org/thread/r7wv36o356nolq7f



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)