Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-972

RHODS Build needs to move the Jira issues (Story + Bugs) from RESOLVED to READY FOR QA state in the workflow

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • RHODS_1.4.0_GA
    • Build and Release
    • 3
    • False
    • False
    • Hide
      1. The RC builds of down stream RHODS include content that is "CDW Release Ack"d ONLY.
      2. The associated Jira items are marked as "READY FOR QA".
      3. The build once it is available is picked up by the RHOSi Master job to trigger the series of quality gates.
      4. Out of scope of this Story : Documentation content -  We are finalizing the flow of documentation content, so we can track that through a separate Jira issue.

       

      Show
      The RC builds of down stream RHODS include content that is "CDW Release Ack"d ONLY. The associated Jira items are marked as "READY FOR QA". The build once it is available is picked up by the RHOSi Master job to trigger the series of quality gates. Out of scope of this Story : Documentation content -  We are finalizing the flow of documentation content, so we can track that through a separate Jira issue.  
    • N/A
    • No
    • Undefined
    • No
    • N/A
    • None
    • MODH Sprint 35, MODH Sprint 36, MODH Sprint 37, MODH Sprint 1.7, MODH Sprint 1.8, MODH Sprint 1.9

      1. RHODS downstream build system on CPaaS that produces the builds needs to do the following.
      2. It needs to ensure that the contents of the RHODS builds have the "CDW Release Ack" set by the CDW Engine.
      3. The Jira items themselves would have reached RESOLVED state before the CPaaS build scripts pick it up, so all the Jira issues, once their code changes are included into the Build, should be moved to "READY FOR QA". This is when QE knows that these items need to be tested.
      4. Ofcourse, the build now produced is a potential RC that can flow through all the Quality Gates and can be pushed to "Stage" and "Prod".
      5. Auto generate a build report with what was approved (ack'd) and built in the image.  Additionally provide the items that were not included that were approved (ack'd) for that version.

              svelosol@redhat.com Samuel Veloso (Inactive)
              giridhar.ramaraju@redhat.com Giridhar Ramaraju
              Pablo Felix Pablo Felix (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: