Is there any way to have a continuous integration in place that does Incremental/Partial Deployment using SalesforceDX. So that only the components that are changed are deployed, instead of a full build.

I got one question here which is almost a year old, which did not mention any solution to it.

Also the documentation (beta version) does not mention anything about it.

  • 1
    Isn't that what a sfdx force:source:push does? Identify the components that have changed and only push those to the org. Or do you want to exclude some of those changed components? – Daniel Ballinger Aug 3 '17 at 22:38
  • its only allowed for scratch orgs...Meesage: You can push source only to a scratch org using this command. Use the Metadata API to sync changes for non-scratch orgs. – San Tosh Aug 3 '17 at 22:48
  • I was looking for Continuous Integration using Travis, to Sandbox or Production environment – San Tosh Aug 3 '17 at 22:49
  • I"m not aware of a sfdx command that will reduce the metadata down to just the changes required to the sandbox or production org. There isn't currently a way to diff with what is currently in the target org and determine which changes are required. At least not without using a third party tool. – Daniel Ballinger Aug 3 '17 at 23:09
  • 2
    We started using GearSet, and it basically does a smart diff to figure out the difference between a branch and an org, and syncs them up. There's other tools out there that do this as well. As far as CI goes... it really depends on the CI. I've heard of intelligent deploys using both Jenkins and Travis, but I don't know the specifics of how this was accomplished. – sfdcfox Aug 3 '17 at 23:40

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.