function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Neel NeelNeel Neel 

Change set deployment process question DEV - SIT - PROD

Hello Friends,

Have a query regarding deployment process to be followed.

We have 3 environments - DEV, SIT and PROD.

1) We will have 8 releases from DEV to SIT in 3 weeks cycle. And we plan to use Change Sets for migrating the code.
2) Now when we need to do deployment to Production, what process should be followed?
     A) Will we deploy all 8 change sets to Production in same sequence as we did in SIT? Is this standard approach?
     B) Do we need to create a new change set keeping track of all objects which were changed from SIT to PROD?
     C) Is there any other  standard apporach which should be followed?

Appreciate all the help!

Cheers,

 
Best Answer chosen by Neel Neel
William TranWilliam Tran
Neel,

   A) Will we deploy all 8 change sets to Production in same sequence as we did in SIT? Is this standard approach?
Yes, the same sequence/process should be followed - if it worked.  The change sets themselves may be different if you have Defects in SIT and have to fix it in SIT directly.  But the process/sequence should be the same.

     B) Do we need to create a new change set keeping track of all objects which were changed from SIT to PROD?
If there are defects and you fixed it in SIT then yes.  IF you fix everything in DEV and migrate the DEV changes to SIT then no, your DEV change sets are the master source for all environments.

     C) Is there any other  standard apporach which should be followed?

Sometime companies have a environment for PreProd or Staging where the final deployment test is done. 
Code sits in there for a few days or longer (this is also known as a freeze period) to see if it had any negative impact on anything else like different lines of business or different integration apps, performance, etc.

Once the freeze is over, you can deploy to PROD.

Thx

All Answers

William TranWilliam Tran
Neel,

   A) Will we deploy all 8 change sets to Production in same sequence as we did in SIT? Is this standard approach?
Yes, the same sequence/process should be followed - if it worked.  The change sets themselves may be different if you have Defects in SIT and have to fix it in SIT directly.  But the process/sequence should be the same.

     B) Do we need to create a new change set keeping track of all objects which were changed from SIT to PROD?
If there are defects and you fixed it in SIT then yes.  IF you fix everything in DEV and migrate the DEV changes to SIT then no, your DEV change sets are the master source for all environments.

     C) Is there any other  standard apporach which should be followed?

Sometime companies have a environment for PreProd or Staging where the final deployment test is done. 
Code sits in there for a few days or longer (this is also known as a freeze period) to see if it had any negative impact on anything else like different lines of business or different integration apps, performance, etc.

Once the freeze is over, you can deploy to PROD.

Thx
This was selected as the best answer
Preeti LalwaniPreeti Lalwani
This is exactly the same reason that Flosum was built for. Please check out the demo at flousm.com