Uploaded image for project: 'A-MQ Messaging-as-a-Service'
  1. A-MQ Messaging-as-a-Service
  2. ENTMQMAAS-2707

Migrate from old cachet plugin to statuspage

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • CI
    • None

      Strimzi referent PR: https://gitlab.cee.redhat.com/strimzi/strimzi-ci/-/merge_requests/135

       

      Hello, I am letting you know that we are ready for users to migrate to
      Cachet replacement known as statuspage.io[0]. This is a new
      implementation of Resource Ready best practice[2], that is going to
      replace the old one.

      We are working with EXD on a timeline to terminate Cachet server
      (running on https://internal.status.redhat.com/), but that is not yet
      finalized. For now, they have asked us to migrate over as soon as we can.

      Please, make an effort to migrate your instance and jobs to
      StatusPage[0]. Feel free to get back to me in case of problems or questions.

      Thank you!

      [0]
      https://docs.engineering.redhat.com/display/CentralCI/Jenkins+Gating+with+StatusPage.io
      [1] https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready

              rhn-support-jkalinic Jan Kalinic
              dkornel@redhat.com David Kornel
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: