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.
Rerun an Existing Pipeline (to Production)
Summary:
Run an existing pipeline again with the recent changes vs. creating a new pipeline.
Content (please ensure you mask any confidential information):
Can I use my existing pipeline that has already pushed to production three weeks ago (24C) again to capture the recent changes have been done (24D)?
Steps, I have done:
- Production branch, deploy and package jobs, a pipeline with these jobs have been created and run three weeks ago (24C)
- In 24D, we made a change and published to main (on TEST instance)
- With a merge request this change has been pulled into the production branch from main
0