Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Other variant of patching required for productive repositories (former MUD repository)
Given
A)
We have a multiuser repository (*.rpd) for developement. This MUD includes thematically structured sub-projects with up to 9 developers.
Some subprojects have been released for publication, others are still under development.
B)
The production repository is the result of merged subprojects. It only contains a subset of sub-projects form the multiuser repository: the sub-projects released for publication. The merge process of sub-projects works as it should. Currently we have about 23 sub-projects published.
All versions of published sub-projects (*.rpds) are archived on the filesystem for further procession (see C).
C)
Sometimes changes have to be made in the published subprojects. From results in deviations compared to the previous version of the sub-project a patch is generated. This patch is applied to the PRODUCTION repository.
The latter procedure causes the problems. THE PATCH FILE DESCRIBES THE CHANGE CORRECTLY, BUT IT ISN'T APPLIED PROPERLY.
Problem
No solution is provided via SR: The support refers to the documentation, which relates the patching to the (entire) development repository ( )
But the suggestet full merge of the latest version of our currently 23 sub-projects - instead of a patch - is no solution, when only a tiny little change in only one sub-project is neccessary. The greater the number of sub-projects, the greater the effort involved in this process.
Required solution
Patches derived from sub-projects of the development repository must be able to be applied to the production repository.
