I'm looking for advice on how other people have resolved this issue.
The issue is that we had config sent to production without ever being tested in QA! This is how:
PROJECT 1:
1) Create CHaRM and config transport request with task
2) Perform config change in table XYZ with key 123 and field 1 has value = A
3) Release Task -> Send to Testing -> Creates TOC and loads to QA with table XYZ with key 123 and field 1 has value = A
4) Test is successful but not ready to move to PRD (can repeat 2-3 as may times as needed to fix issues)
Before releasing to Production...
PROJECT 2:
5) Create CHaRM and config transport request with task
6) Perform config change in table XYZ with key 123 and field 1 has value = B (different than for Project 1) - It is added to Project 2's transport task (correctly so) but there is no lock put on from Project 1 CHaRM on the object key so no warning....
Back to Project 1 that is now ready to move to production
7) CHaRM released to production -> Transport request is released
😎 This release takes the current config entry in table XYZ with key 123 and field 1 with value = B AND NOT the TOC entry which had in table XYZ with key 123 and field 1 has value = A (the correct one for this project)
9) This release was done because QA approved it but the entry going to be copied to PRD is now different to what was tested!!!
The only way around this is to released the Transport REQUEST sooner in the process, as soon as QA testing is done. You would almost use the TOCs to QA as a "unit test" environment before fully releasing the request to conduct full QA testing to ensure that the code / config tested in QA is what will go to PRD.
OR you have to find some tool that will compare configuration between Dev, QA and PRD to find discrepancies on all config entries that you are going to change (not practical)
Thoughts?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.