Recently in my project I have been asked to switch to multiple migration path technique. As of today we have one integration testing environment and one User acceptance testing environment.
Now in future we are going to have two Integration (say I1 and I2) and two user acceptance (say U1 and U2) testing environment. This is to support more projects testing in a year.
I1 -> U1 -> PROD
I2 -> I2 -> PROD
Both the paths will be used for separate release with the implementation dates at least a month apart. Now if my same code is bundled in both the release and testing is in progress, how can I maintain the code integrity in the test environment. As of today we are doing manual retrofitting of components which is prone to human errors. Is there a automated tool available which does a retrofitting and deploys the correct component to production based on install dates. Is there a IBM defined process to handle this scenario?
Joined: 20 Oct 2006 Posts: 6962 Location: porcelain throne
unless you have committed management resources to insure success,
this is just another BS way for beancounters to double bill.
the reconciliation process is no fun when the changes are minor and do not overlap.
when they are numerous and physically overlap,
you need dedicated resouces whose attributes are not limited to:
if they give this job to the rookies, start looking for employment elsewhere.
Endevor (if you have it) has a Parallel Development Management (PDM) option which does a good job of identifiying the differences.
Previously, this type of activity was accomplished by SUPERC compares.
but it is not something that can be automated.
if the differences are complex,
someone must make a manual decision.