We are using Github as our source control and Drone.io CI/CD pipelines to handle builds and releases to multiple sandbox environments and our production environment. We would like to use destructivechangespre.xml and destructivechangespost.xml to reduce manual work related to each release.
I know that when you deploy a release that contains destructive changes a second time to an environment you will get errors related to not being able to delete the metadata components that are in your destructivechanges file(s) due to them not existing (since they were already deleted during the first deployment, of course). I've also heard that you can get around this issue by appending the --ignorewarnings tag to your deployment command.
My questions are:
- Is it the --ignorewarnings tag that is appropriate to use for this case or --ignoreerrors?
- Whichever tag will allow us to circumvent this warning/error, does it work when deploying to a Production environment?