• Icon: Task Task
    • Resolution: Won't Do
    • Icon: L3 - Default L3 - Default
    • 3.7.0-alpha1, 3.7.0
    • None
    • 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

        This is the controller panel for Smart Panels app

            [OPT-5622] Resolve Zeebe parallel test conflicts

            Joshua Windels created issue -
            Joshua Windels made changes -
            Status Original: Open [ 1 ] New: In Specification [ 10000 ]
            Joshua Windels made changes -
            Status Original: In Specification [ 10000 ] New: In Development [ 10312 ]
            Sebastian Bathke made changes -
            Labels Original: current_release New: next_release
            Eric Lundberg made changes -
            PM Priority New: 2
            Omran Abazeed made changes -
            Labels Original: next_release New: current_release next_release
            Omran Abazeed made changes -
            Labels Original: current_release next_release New: current_release
            Joshua Windels made changes -
            Assignee Original: Joshua Windels [ joshua.windels ]
            Resolution New: Won't Do [ 10101 ]
            Status Original: In Development [ 10312 ] New: Done [ 10010 ]
            Joshua Windels made changes -
            Mentioned Roles
            Joshua Windels made changes -
            Mentioned Groups

              Unassigned Unassigned
              joshua.windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: