Skip to main content
Solved

Release Update 22R2 - Can we have 2 different topic branches for different steps in release update

  • November 29, 2022
  • 4 replies
  • 198 views

srinivas
Sidekick
Forum|alt.badge.img+7

 

Hi,

 

During the release update process, can we have 2 topic branches ,

 1 topic branch for “Customization Upliftment Preparation” step completion and

another topic branch for “Order Topic Environment” step( Provided both branches have same code files) ?

 

Regards,

Srini

Best answer by Jeewaka Padmapriya

Hi @srinivas,

According to the Technical Documentation, you should use the same topic branch created in the “Customization Upliftment Preparation step” till Merging the uplifted customizations to customer-solution repository release-update branch. Please refer to the below documentation.

https://docs.ifs.com/techdocs/22r2/020_lifecycle/090_release_update_studio/050_impact_analysis_and_cust_upliftment/020_apply_to_sol_and_cust_upliftment/

If there are multiple developers are working on uplifting customizations, they need to share the same topic branch created in the preparation step and the pull requests need to be created by a single developer. 

Once the uplifted customizations are merged to customer-solution repository release-update branch, you may create multiple ru-topic branches pointing to the release-update branch in the Customer Solution Repository.

Hope the above response helps!

Cheers!

View original
Did this topic help you find an answer to your question?

4 replies

srinivas
Sidekick
Forum|alt.badge.img+7
  • Author
  • Sidekick
  • 10 replies
  • November 29, 2022

@Rusiru Dharmadasa - Any thoughts on this please


Rusiru Dharmadasa
Superhero (Employee)
Forum|alt.badge.img+20

@Jeewaka Padmapriya  will check this and help us here :)


Jeewaka Padmapriya
Hero (Employee)
Forum|alt.badge.img+10

Hi @srinivas,

According to the Technical Documentation, you should use the same topic branch created in the “Customization Upliftment Preparation step” till Merging the uplifted customizations to customer-solution repository release-update branch. Please refer to the below documentation.

https://docs.ifs.com/techdocs/22r2/020_lifecycle/090_release_update_studio/050_impact_analysis_and_cust_upliftment/020_apply_to_sol_and_cust_upliftment/

If there are multiple developers are working on uplifting customizations, they need to share the same topic branch created in the preparation step and the pull requests need to be created by a single developer. 

Once the uplifted customizations are merged to customer-solution repository release-update branch, you may create multiple ru-topic branches pointing to the release-update branch in the Customer Solution Repository.

Hope the above response helps!

Cheers!


srinivas
Sidekick
Forum|alt.badge.img+7
  • Author
  • Sidekick
  • 10 replies
  • December 5, 2022

Thank you Jeewaka.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings