Remove the CamBPM engine dependency from the Zeebe Integration Tests

XMLWordPrintable

    • M

      Context

      The build pipeline has an extra stage for executing the Zeebe integration tests. Currently this stage requires the Camunda BPM Engine. Furthermore, AbstractZeebeIT still inherits the engine extensions.  

      Steps to reproduce:

      1. Start a build pipeline (e.g. push something in a Github PR)

      Actual result :

      The test stage "IT Zeebe" requires CamBPM

      Expected result:

      IT Zeebe stage should still work when this commented is removed from the Jenkinsfile (camBpmContainerSpec(camBpmVersion, false, 6, 4). AbstractZeebeIT still inherits the engine extensions, we should separate these having a real AbstractIT without cambpm or zeebe specifics but just optimize and elasticsearch extensions as well as AbstractCamundaPlatformIT & AbstractZeebeIT

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Giuliano Rodrigues Lima
              Giuliano Rodrigues Lima Giuliano Rodrigues Lima
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: