Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-3818

SQL patch scripts are missing exact version number in distribution

XMLWordPrintable

      Problem:

      The SQL patch scripts for enterprise versions are missing the exact version numbers where they should be applied. Instead they are all concatenated into a single big file '<version>_patch.sql' for each minor version.

      AT:

      • We do not lose the version numbers for the sql patch scripts.
      • SQL upgrade tests, instance-migration still work

        This is the controller panel for Smart Panels app

            [CAM-3818] SQL patch scripts are missing exact version number in distribution

            Robert Gimbel added a comment -

            Discussion results:

            • upgrade scripts are always independent from patch scripts
            • it is documented in minor version and patch level upgrade guide which patch scripts exist (including reference to ticket and info which index is created)
            • developer guide contains the following info
              • patch scripts are never part of upgrade
              • create scripts and drops scripts are adjusted

            Robert Gimbel added a comment - Discussion results: upgrade scripts are always independent from patch scripts it is documented in minor version and patch level upgrade guide which patch scripts exist (including reference to ticket and info which index is created) developer guide contains the following info patch scripts are never part of upgrade create scripts and drops scripts are adjusted

            Christian added a comment -

            See https://app.camunda.com/confluence/display/camBPM/SQL+Patch+Scripts

            Christian added a comment - See https://app.camunda.com/confluence/display/camBPM/SQL+Patch+Scripts

            Robert Gimbel added a comment -

            Why did you use confluence for the developer guide?

            Shouldnt we use this one here in the docs: http://docs.camunda.org/latest/guides/developer-guide/

            ?

            Robert Gimbel added a comment - Why did you use confluence for the developer guide? Shouldnt we use this one here in the docs: http://docs.camunda.org/latest/guides/developer-guide/ ?

            Maintenance added a comment -

            When I talked about developers I meant our core developers so they know
            which files to add/modify in case we have to provide another patch script.
            No public audience.

            Maintenance added a comment - When I talked about developers I meant our core developers so they know which files to add/modify in case we have to provide another patch script. No public audience.

            Robert Gimbel added a comment -

            I think that is what the developer guide is for. From my side it is ok to put it in there

            Robert Gimbel added a comment - I think that is what the developer guide is for. From my side it is ok to put it in there

            Christian added a comment -

            Alright, I'll transfer it.

            Christian added a comment - Alright, I'll transfer it.

            Robert Gimbel added a comment -

            great thanks

            Robert Gimbel added a comment - great thanks

            Christian added a comment -

            I added an assembly to zip / tar the sql-scripts up additionally

            Christian added a comment - I added an assembly to zip / tar the sql-scripts up additionally

            Sebastian Menski added a comment -

            Cool thanks.

            Sebastian Menski added a comment - Cool thanks.

              matthijs.burke Matthijs
              lipphardt Christian
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: