Deployment of 'Live only' code

Discussion created by DanielGates628573 on Nov 16, 2017
Latest reply on Nov 17, 2017 by Wolfgang_Brueckler_1288

As part of a new deployment there are certain jobs that must not run when deployed to a none live environment/client.  Here are the options I have thought of so far:

1. Deploy all the jobs to all environments and remove the actual code (using powershell) in the process tab when we deploy the objects to none live environments.
2. Deploy all the jobs to all environments and then create a list of live jobs and ensure these cannot be activated on a none live environment.
3. Deploy all the jobs to all environments and then enforce a naming convention of the objects so we can identify a live only object and then ensure these do not run on a none live environment.
4. Do the same as point 3 but use one of the archive keys to flag a live only job.

From what I can see all of the options have their flaws with potential for user error ...

Has anyone had any similar issues and which method would be recommended? or any other suggestions would be great..

If it provides any assistance the live and none live clients will run against their own automic engine.

The preferred option is to remove/add in the live code when we deploy to none live/live environments ... that way the call to a live unix script for example is never in automic for none live environments ..