This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

<@UAA1TMMTR> we have a pretty advance deployment process here, and we started looking into having a setup where update to the git master would trigger sdfcli to update any object/scripts in it. So developers don't need production access anymore/unless emergency. But at some point it gets really tricky:
1: Any new sdfcli setup/environment will "touch" all files in NetSuite, even if there is no changes, losing the real lastmodifieddate of files
2: Dependency cannot be cascaded automatically, needs to be done in steps.

So we started looking to per task/branch deploy.xml but it can still be tricky on chain dependencies, and we would end up with a lot of different deploy.xml.

Is it a process we should give up  ?

my recommendation was for NetSuite to host a remote git repo that we would check into and do PRs to

this would allow for a managed development environment across an infinite number of accounts

unfortunately, there are a lot of NS clients and a lot them use non-git VCS