Closed orvischoinierec closed 1 year ago
As already stated in the readme and the b2c-crm-sync documentation, the CLI commands provided in the repository ARE NOT HERE TO BE USED TO DEPLOY TO PRODUCTION.
Please create a proper CI/CD and release management process to deploy to your production org safely.
@orvischoinierec Hi Sir, we are facing the same issue, all the components are deployed but the test are failing and thus it is rolling back our deployment to unscussefull in production.
Did you resolve the issue? if yes could you please guide me.
Thanks, AShok
@avarma4213 Were you able to resolve the test class errors during deployment to production.
Describe the bug
We're trying to deploy to our production org using the CLI. We've set up the .env settings appropriately and are able to make all necessary connections. However, we are stuck trying to deploy our metadata
We receive the following error when trying to execute the deploy command. We also have personaccounts enabled so this command deploys both base and personaccounts
Command
npm run crm-sync:sf:org:deploy
Output
In order resolve this issue we added the following lines to
lib/cli-api/_sfOrgDeploy.js
After adding these lines we get the following error
Expected behavior Metadata should deploy
Your local environment details:
node -v
): v15.2.1npm -v
) v7.0.8sfdx -v
) sfdx-cli/7.153.1 darwin-x64 node-v16.15.0Your remote environment details:
Additional context
There doesn't appear to be any solid instructions on how to deploy this project to a production org. If there is an established way to move metadata to a production org please document how this is done. We looked into change sets however there are so many files it did not seem feasible. Help with this error or guidance on how to move our metadata and this project to production would be greatly appreciated. We are all set on the commerce cloud side as we have deep experience there.