Story (Required)

A new version of CPaaS will be available by February 28th and provides important security updates. All CPaaS users will need to update to this version of CPaaS before March 13th

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