Uploaded image for project: 'Red Hat OpenBridge'
  1. Red Hat OpenBridge
  2. MGDOBR-414 Investigate and define initial tasks to start the onboarding process for CPaaS
  3. MGDOBR-620

Configure midstream sync

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • False
    • None
    • False
    • OpenBridge Sprint 216, MAS CCS - Sprint 217, MGDOBR - Sprint 218, MGDOBR - Sprint 219, MGDOBR - Sprint 220, MGDOBR - Sprint 221, MGDOBR - Sprint 222, MGDOBR - Sprint 223, MGDOBR - Sprint 224, MGDOBR - Sprint 225, MGDOBR - Sprint 227, MGDOBR - Sprint 228, MGDOBR - Sprint 229, MGDOBR - Sprint 230

      Issue Description: 

      The midstream automation feature allows CPaaS to update the midstream repo when a new commit is pushed to the upstream repo(s), propagating those changes to the dist-git repos.

      Follow the CPaaS documentation to ensure the midstream repo contains the necessary files and structure to enable the midstream automation:

      https://cpaas.pages.redhat.com/documentation/users/midstream/adding_new_project.html#_enable_midstream_automation

      Acceptance Criteria:

      CPaaS Jenkins Pipeline should be triggered on every push on external GitHub repo

              vajain Vaibhav Jain
              vajain Vaibhav Jain
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: