Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3886

Configure m2, m3, stg cluster access tokens, update periodic reports logic

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Currently the logic of obtaining OC client from the cluster and getting deployment verison has been all squashed to m1 cluster directly.

      In the future we want this to be cluster-specific.

      I need to set up access tokens for m2, m3 and stg clusters, put them into crw-jenkins and update the pipelines

              tdancs Tibor Dancs (Inactive)
              tdancs Tibor Dancs (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 2 days Original Estimate - 2 days
                  2d
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 days
                  3d