How to Skuidify our development, deploy and release process? (Git, multi dev orgs, packaging org, Trialforce)

  • 1
  • Question
  • Updated 2 years ago
  • Answered
The development and release process we implement is the following: each developer has its own Dev org (we use Git) and all approved changes are deployed into a common Developer org, from there we deploy to QA org and finally to the Packaging org (the one with our managed package namespace and linked to our Appexchange account). Our app will be distributed through Trialforce only so no post-install scripts are available.

I wonder how should we Skuidify our entire process because so far in the docs are straight forward instructions for the scenario to develop the app directly in the packaging org right?
Photo of Sebastian Canseco

Sebastian Canseco

  • 358 Points 250 badge 2x thumb
  • excited

Posted 4 years ago

  • 1
Photo of Don Souza

Don Souza, Employee

  • 1,160 Points 1k badge 2x thumb
Skuid supports accessing multiple Salesforce orgs, so you could use one org (packaging) to view and manage what's occurring in other orgs: dev, qa. Would an approach like this work for you?

http://help.skuid.com/m/models-conditions-filters/l/522611-access-data-across-multiple-salesforce-or...