Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-4165

Create separate user accounts for the post stage deploy test pipeline

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Automation
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • subs-swatch-lightning

      Both the periodic Subscription Watch Test Suite and the post stage deploy test suite are using the same users.  They also can run at the same time.  And they run some of the same tests.
      Table of the accounts:
      https://inscope.corp.redhat.com/docs/default/component/swatch-internal-docs/testing-quality-engineering/pipeline-summary/

      Have the post stage deploy tests use separate users from the post stage deploy tests:
        - The 'user's can stay the same.  But they need to have different usernames, org_ids, and account_ids as defined in the vault.
        - post_stage should be defined in conf/rhsm_subscriptions.default.yaml
        - users should reference new vault entries
        - modify the build pipeline to use the post_stage env instead of stage env.

      Modifying the post_stage pipeline because the others env_check and periodic Subscription Watch Test Suite use a Jenkins file lock to make sure only one runs at a time.

      Acceptance critera:
        - post stage deploy tests will run with different usernames.

              Unassigned Unassigned
              buschv Vanessa Busch
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: