Get Started with Redwood for Oracle Cloud HCM Begin Now
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.
Redwood - pipelining VBS config changes from Dev2 to Prod
Summary:
We are about to start production build and I have a query regarding pipelining VBS config changes from Dev2 to Prod.
We have successfully piped numerous business rules from Dev2(VBS pod) to Test pod, repeatedly using the same project and workspace.
My question is, if we now pipe once from Dev2 to Prod for the first time, will all the consecutive changes we have previously done be bundled up in one package and moved in one go?
We assume so but do not want to take it for granted.
I understand that the source and target pods must be on the same release (24C by the time we do this)
Tagged:
0