Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-6295

Release job does not set previousVersion to preview release

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Won't Do
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • ci
    • None
    • Not defined

      Context:

      During the last preview release, we noticed that the release job set the previous version to 3.8.0 when it should be 3.9.0-preview-1. This then lead to issues when validating the schema version against to to/fromVersions of the upgradePlans when running migrationIT. We should adjust the release job to instead set the previous version to the respective preview release.

       

      See here:

      https://github.com/camunda/camunda-optimize/blob/master/.ci/pipelines/release_optimize.groovy#L245 

       

      AT:

      • release job correctly sets preview releases as previous versions

        This is the controller panel for Smart Panels app

            [OPT-6295] Release job does not set previousVersion to preview release

            Helene Waechtler created issue -
            Helene Waechtler made changes -
            Description Original: *Context:*

            During the last preview release, we noticed that the release job set the previous version to 3.8.0 when it should be 3.9.0-preview-1. This then leads to issues when validating the schema version against to to/fromVersions of the upgradePlans when running migrationIT. We should adjust the release job to instead set the previous version to the respective preview release.

             

            See here:

            [https://github.com/camunda/camunda-optimize/blob/master/.ci/pipelines/release_optimize.groovy#L245] 

             

            *AT:*
             * release job correctly sets preview releases as previous versions             		New: *Context:*

            During the last preview release, we noticed that the release job set the previous version to 3.8.0 when it should be 3.9.0-preview-1. This then lead to issues when validating the schema version against to to/fromVersions of the upgradePlans when running migrationIT. We should adjust the release job to instead set the previous version to the respective preview release.

             

            See here:

            [https://github.com/camunda/camunda-optimize/blob/master/.ci/pipelines/release_optimize.groovy#L245] 

             

            *AT:*
             * release job correctly sets preview releases as previous versions
            Sebastian Bathke made changes -
            Assignee New: Sebastian Bathke [ sebastian.bathke ]
            Sebastian Bathke made changes -
            Assignee Original: Sebastian Bathke [ sebastian.bathke ]
            Joshua Windels made changes -
            Labels Original: next_release New: current_release next_release
            Joshua Windels made changes -
            Labels Original: current_release next_release New: current_release
            Sebastian Bathke made changes -
            Assignee New: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ]
            Status Original: Open [ 1 ] New: In Kickoff [ 11412 ]
            Sebastian Bathke made changes -
            Status Original: In Kickoff [ 11412 ] New: Backlog [ 11212 ]
            Sebastian Bathke made changes -
            Labels Original: current_release
            Joshua Windels made changes -
            Rank New: Ranked lower

              Unassigned Unassigned
              helene.waechtler Helene Waechtler
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: