Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
looking for best practices to deploy VBS changes across different versions
Summary:
Is it required to have one DEV pod to be on Prod cadence always so that no there will not be impact on VBS deployments during upgrade window?
Content (please ensure you mask any confidential information):
We have multiple DEV pods , 1 TEST and 1 PROD pods. Upgrade follows 6 week schedule. TEST and PROD pods are on same patch cadence.
e.g. 25A will be applied to DEV pods on 2/7/25 and after 6 weeks, TEST and Production pods would be upgraded on 03/21/25.
Especially during upgrades, since DEV will be on 25A, Prod and TEST are on 24D, System does not allow VBS deployments from DEV to PROD / DEV to TEST for 6 weeks.
Tagged:
0