Resolve Zeebe parallel test conflicts

XMLWordPrintable

    • Type: Task
    • Resolution: Won't Do
    • Priority: L3 - Default
    • 3.7.0-alpha1, 3.7.0
    • Affects Version/s: None
    • Component/s: backend, ci
    • None
    • 2
    • Not defined

      In Jenkins, we now see port collision errors in the zeebe broker when running tests in parallel. We should make sure each embedded broker is assigned it's own dedicated thread per fork, to avoid this problem

      Hints:

      • We already do something similar for our mock servers, appending the fork number to a dedicated numerical prefix. We can probably do something similar here

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

              Created:
              Updated:
              Resolved: