• Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • fuse-7.12-GA
    • None
    • Fuse Standalone
    • None
    • Very Likely

      From Fuse 7.12, we have new pipelines and they need to be monitored that all the steps have been executed.

      Pipelines to monitor for Fuse Standalone:

      Standalone Guardian Duties:

      • Verify that new versions has been successfully propagated https://fuse-7x-jenkins-csb-fuse-qe.apps.ocp-c1.prod.psi.redhat.com/job/fuse-7.8-update-projects
      • Monitor all the Standalone pipelines and notify team about the progress -> Started, Failed, Successful, Finished -> Google Group Chat
      • Make sure all steps/tests/parts of pipelines have been executed
      • If you encounter a problem/failed steps, try to troubleshoot it or ask people for help e.g. Group Chat
      • If there is any bug in pipeline, document it and let Team Leaders know
      • Check if we have right values like parameters. We have to have build completed and with right day.
        • example: event": "progressInfo": {"completed": true}

          " and "productization-build-completed" and "version":"7.12","build":"CR1.2020.06.25.00"

        • The result of stages can be evaluated through Greenwave service as well (see gating section)

      Few notes about pipelines:

      • fuse-7.12-pipeline-umb-trigger -> It's uber trigger, that is triggering all Fuse Standalone and Fuse On OpenShift pipelines. It's consumes messages from UMB topic and send it forwards
      • fuse-7.12- {karaf|spring-boot-2|eap}-pipeline -> the standalone pipelines

              tveskrna Tomas Veskrna
              fuseqe Fuse QE (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: