@erictgrubaugh similar to your case, I wish that I could have a

deploy_staging.xml

, or a

deploy_production.xml

. So that the deployment file is passed in as a parameter

Hey David, you are not the only one that has requested this feature. Could you provide more information on the use case for this requirement? Thanks

While I haven't done this myself, I can definitely see it being useful, particularly when you have Sandbox available. Settings on things like Script records are often intentionally different between the two environments, and you don't want to constantly have to flip them (e.g. Testing -> Released and back, changing Audiences, etc)

Sure, and like Eric said too, having DEBUG enabled in sandbox environments, but ERROR in production environments. Or having sandbox/production specific script parameters. In my particular case I have all of our suitescripts in a single repository, as i'm working on sprint1, i'd like to have something like a

deploy_sprint1.xml

, for when it goes to production. And at the same time i'll be working on a

deploy_sprint2.xml

@Carlos Olivares (NS DevTools PM) take your notebook! 🙂