The CreatorCon Call for Content is officially open! Get started here.

Originating environment vs current environment in App engine deployment request

NARENDRA KAMMIL
Tera Contributor

Quick question , 

 

when a deployment request is created to move code from dev to test and then to prod 

 

How this deployment request works ?

 

Will the code moves from Originating environment  to all targets ?  or 

will it moves from Originating environment   to current environments and then from Current to target ?

 

My question is If app is moved from Dev to Test ( if we have any issues In Test as we updated some code ) 

once the 2nd level approval is approved , will the code from Target pushes to Prod  ? or Dev to Prod ?

2 REPLIES 2

Paige Duffey
ServiceNow Employee
ServiceNow Employee

Hello, I've added some data to this little diagram. Let me know if it helps. But if you make changes in Dev AFTER the DR is submitted, the DR will need to be cancelled and then resubmitted with the new app version.

 

PaigeDuffey_0-1713446721751.png

 

Thank you so much for your reply , The issue we are facing here is We deployed code via updatesets in Test and Hi team mentioned that we are not supposed to push via updatesets , as it might break some version stuff. We backedout our Application updatesets and pushed via deployment request from Dev to Test ( half of the variables are missing which broke the application) and now in the deployment request we see another approval and it will move to prod once approved. My question here is Will the code from Test push to Prod or from Dev to Prod ?

 

If it moves from Dev to Prod ( it is good as We tested pushing to another fresh instance and it worked well) 

 

NARENDRAKAMMIL_0-1713448229993.png