Uploaded image for project: 'OpenShift Jenkins'
  1. OpenShift Jenkins
  2. JKNS-964

[CPaaS] Update CPaaS instance to v9.35.0 for Jenkins

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.13, 4.12, 4.14, 4.15, 4.16, 4.17, 4.18, 4.19, 4.20
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False

      Story (Required)

      CPaaS instances are required to update to version v9.35.0 before December 30th. This update is required to address the deprecation of the PSI Ceph storage that provides the S3 buckets for CPaaS. See CPAAS-6224 for more information.

      Any instances that have not been updated by the required date will fail the build pipeline when trying to store build result information in the S3 storage buckets. Instructions for upgrading are available in the upgrading to new CPaaS version documentation..

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      The Jenkins CPaaS build configuration needs to be updated to work with the new CPaaS release.
      https://gitlab.cee.redhat.com/cpaas-products/openshift-jenkins

      How to Upgrade
      https://cpaas.pages.redhat.com/documentation/users/cpaas_version_updates/upgrading_to_new_cpaas_version.html

      cPaaS releases
      https://gitlab.cee.redhat.com/cpaas/service/-/releases

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              rh-ee-kmemane Kunal Memane
              rhn-support-prdhamdh Prashant Dhamdhere
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: