function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Darrell DeVeaux 7Darrell DeVeaux 7 

Best Practices on Organizing Zip and Other Development Files?

I'm sure been asked before but is there a good resource or thoughts on organizing all the related zip files, etc for development that an ISV partner might use? For instance, originally we had some items by customer with specific assets stored there. (Test Data, customizations, etc.) Other ways to organize?
Raj R.Raj R.
Hi Darrell,

Have you already explored option like GitHub (https://github.com/), GitLab (https://about.gitlab.com/), or BitBucket (https://bitbucket.org/) (many more) for your development files?.

I would recommend using a tool like force-dev-tool (https://github.com/amtrack/force-dev-tool), which is similar to Salesforce DX (https://developer.salesforce.com/tools/sfdxcli) to help manage those development files more easily. I have used it on many Salesforce orgs and makes deploying of features in small increments. It allows you to get just the files that were modified so you can send those to any at any given time. It also has ways to setup and save your Test Data. 
Darrell DeVeaux 7Darrell DeVeaux 7
I need to clarify question a bit more. We have DX and CircleCI. My question is regardless of which tools using (IDE, Git, etc.), how some of the files are organized esp around consistent assets. If you have DX projects setup by customer but a number of those classes, assets are consistent across customers what are some ways those are setup. DX is a bit new and we've only used sparingly up to this point but is large reason for question so we setup this part in good way to start.

For instance, if you have Flows in your package that are used by 4 customers and you make a change to 1 that you will eventually deploy to all 4 of those customers, do you have centralized "flows" project? If not how doing?