0

I've deployed many times to SFDC using the Force.Com Migration Tool & Ant. In many cases I often end up having to undertake manual steps to get around issues. An example being Flows. Flows cannot overwrite actively running flows in the org where the deployment is being deployed to. When deploying I've had to deactivate and delete flows to allows flows to be overwritten. This is an example of an issue I wondered how CI can get over? There are other issues which arise sometimes which also requires a manual change. I wanted to know if anyone has any tips on how to setup CI in such a way that it can get over any such similar issues? Is there a rule in how the package.xml is broken down. Should the package be broken into different Sub-Unit packages instead of one package which contains all?

Are there golden rules which can be applied to resolve known issues?

Thanks in advance.

  • 1
    FYI I saw a Gearset demo a while ago where that (paid for) tool handled some of these problems. – Keith C Apr 24 '17 at 17:20
  • Thanks Keith. Flows are the main bug-bear. Generally I'm not sure if errors can be removed without manual intervention. – RedQueries Apr 27 '17 at 8:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.