function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Paul Fitzpatrick 19Paul Fitzpatrick 19 

Pitfalls of pushing Apex and Visualforce in Change Sets from Sandbox to Production

I have inherited the maintenance of some Visualforce and Apex code. I have downloaded the
Eclipse project, and am using the Force.com IDE. I created two Developer
Sandboxes (recently refreshed from Production), and want to "push" minor
changes between these two Sandboxes to make sure everything is Ok. I have
made Visualforce and Apex changes in one Sandbox and was able to deploy and
"see" the changes locally in that Sandbox, but I don't yet fully understand the
pitfalls of pushing "Apex and Visualforce" in Change Sets from Sandbox to
Sandbox(or ultimately Sandbox to "Production"). Can you please point me to relevant documentation! Thanks!
Jerome RussJerome Russ
Hello! The easiest thing I can think of is the Trailhead module for Application Lifecycle Management: https://developer.salesforce.com/trailhead/en/module/alm_deployment

There are also some good points made here but keep in mind Flosum is a tool to replace Changesets:
http://www.flosum.com/limitations-of-changesets/
Paul Fitzpatrick 19Paul Fitzpatrick 19
Hi Jerome, Thanks for this! Let me take a look, and if I still have questions, perhaps you can assist when you get a free moment?