Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
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.

Suggestion for deployment on Production

Summary:

We would like to know best approach for deployment on Production in the following situation we are in:

Our Situation

We have directly published all changes in our test environment for Goals, Performance, Absence module. So, the code changes went directly to main branch and pipeline initiated the deployment in test environment successfully

Now we want to move only changes related to Goals in production environment.

We have not created any branch from main when we started publishing respective modules changes. However, we followed the convention of putting comments on each personalization published by each individual developer for each module.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!