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

Stabilize nightly sequential upgrade pipeline

    Details

    • Type: Task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.5.0
    • Component/s: backend
    • Labels:

      Description

      Our nightly sequential upgrade pipeline sometimes fails if there is no xml yet imported for a given decision definition. This happens due to the test script only asserting a certain process instance count and as these are already fully imported by the import of an earlier version the 2.3.0 instance get's killed before it can successfully import decision definition data.

      At best we wait for the import to be signaled complete before killing a particular optimize instance using the status endpoint.

      https://ci.optimize.camunda.cloud/view/all/job/upgrade_multiple_releases_sequentially/25/consoleFull

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            sebastian.bathke Sebastian Bathke
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: