Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-12712 Create general pipeline structure
  3. CAM-12788

Develop strategy for artifacts in multi-pipeline executions

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.15.0-alpha2, 7.15.0
    • None
    • None
    • None

      Given:
      A developer making a code contribution to the Process Engine. The contribution may span only the CE or EE repository, or both.

      When:

      1. Contributing to the CE repository
      2. Contributing to the EE repository

      Then:
      We should check how/when artifacts are transferred, and what EE branches are used.

      E.g.:

      1. Contributing to the CE repository
        • We should check if a branch of the same name is available in the EE repository.
          • If it's present, we should use that branch.
          • If it's not present, we should use the master branch.
      2. How do we make sure that, in a CE+EE contribution, a push to the EE repo doesn't trigger a standalone EE-pipeline execution?

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              nikola.koevski Nikola Koevski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: