Make deployable branches work with a dedicated DB

XMLWordPrintable

      Infra gave us the possibility to deploy branches as part of https://jira.camunda.com/browse/INFRA-1617. However, these changes were rolled back on infra's recommendation due to limitations expressed as part of https://jira.camunda.com/browse/INFRA-1235. The problem is mostly that they are all sharing the same static DB, which is also the same as that used by stage. This also means that any deploy would reset and seed the DB (and in turn affect all environments using this DB). Considering that this feature is not used much by Optimize at the moment, a rollback was considered the best option for now with a view to exploring how we can better support this in future, perhaps by using smaller short-lived containers instead.

            Assignee:
            Unassigned
            Reporter:
            Joshua Windels
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: