We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-7428

Backport release pipeline to maintenance branches

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.12.0-alpha2
    • None
    • None
    • Not defined

      *Description of the problem:*
      Currently, the release pipeline is only available on master. After syncing with Maxim Danilov we thought it would be actually a good idea to have it backported to the maintenance branches since in the future the Dockerfiles across versions could end up diverging or there might be a different requirememt introduced for each release version.

      *Desired outcome and acceptance tests:*
      The release has to be backported in the following branches:

      • maintenance/3.7
      • maintenance/3.9
      • maintenance/3.10
      • maintenance/3.11

      Link to the prs:
      https://github.com/camunda/camunda-optimize/pull/9377
      https://github.com/camunda/camunda-optimize/pull/9378
      https://github.com/camunda/camunda-optimize/pull/9379
      https://github.com/camunda/camunda-optimize/pull/9380

      Testing:
      In each pr there is a dry run of the release to be found

        This is the controller panel for Smart Panels app

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

            Backport release pipeline to maintenance branches

              • Icon: Task Task
              • Resolution: Fixed
              • Icon: L3 - Default L3 - Default
              • 3.12.0-alpha2
              • None
              • None
              • Not defined

                *Description of the problem:*
                Currently, the release pipeline is only available on master. After syncing with Maxim Danilov we thought it would be actually a good idea to have it backported to the maintenance branches since in the future the Dockerfiles across versions could end up diverging or there might be a different requirememt introduced for each release version.

                *Desired outcome and acceptance tests:*
                The release has to be backported in the following branches:

                • maintenance/3.7
                • maintenance/3.9
                • maintenance/3.10
                • maintenance/3.11

                Link to the prs:
                https://github.com/camunda/camunda-optimize/pull/9377
                https://github.com/camunda/camunda-optimize/pull/9378
                https://github.com/camunda/camunda-optimize/pull/9379
                https://github.com/camunda/camunda-optimize/pull/9380

                Testing:
                In each pr there is a dry run of the release to be found

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        andromachi.rozaki Andromachi Rozaki
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              andromachi.rozaki Andromachi Rozaki
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              1 Start watching this issue

                                Created:
                                Updated:
                                Resolved: