You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "deploy" target defined in build.xml depends on "undeploy". Looking at undeploy.xml, it generates a destructiveChanges.xml file that effectively purges all custom components from the org. This happens without prompting. Is this intended behaviour?
In our case, it happened against a relatively fresh sandbox, but if that happened against a mature sandbox (or against production), it could cause some serious headaches for users, especially if their backups aren't up to date.
The text was updated successfully, but these errors were encountered:
These files are really to support the CI into Travis and are not intended to be used for this purpose. To avoid this confusion i guess a big note in the Ant file would be a good idea. 👍
The "deploy" target defined in build.xml depends on "undeploy". Looking at undeploy.xml, it generates a destructiveChanges.xml file that effectively purges all custom components from the org. This happens without prompting. Is this intended behaviour?
In our case, it happened against a relatively fresh sandbox, but if that happened against a mature sandbox (or against production), it could cause some serious headaches for users, especially if their backups aren't up to date.
The text was updated successfully, but these errors were encountered: