Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When i change any data into salesforce code using eclipse and trying to save that then eclipse takes too much time but when i am doing this thing in sandbox it will get saved , deployed and synchronized quickly .

Is there any way to decrease the delay between saving , deploying and synchronizing the code to server using eclipse or any other tool?

enter image description here

share|improve this question
Most likely not, the reason its taking so long is that all tests in production are being executed when you push in any code. This is not the case in a sandbox, where no tests get executed. – BarCotter Feb 24 '14 at 13:52
BarCotter - you should post this as an answer, as its spot on. – Bob Buzzard Feb 24 '14 at 13:54

Its not possible to speed up the deploy to a production instance. The reason its taking so long is that all tests in production are being executed when you push in any code. This is not the case in a sandbox, where no tests get executed.

If you are using two separate orgs (dev and sandbox) for development, which it seems you are based on your diagram. Then production should not be the org where you combine both codebases. Untested code should NEVER be deployed into a production environment. You should consider syncing up your dev org and sandbox so that they have the same copy of all code or introduce a new sandbox as shown below

Updated overview

share|improve this answer
Is there any way to stop the test cases while saving the code onto server using eclipse or any other tool ? – Amit Agrawal Feb 24 '14 at 14:08
No, its not possible to save to a production org without all tests being run. This is to insure that there is at least 75% test coverage and that all tests pass. It also makes sure that your code hasn't broken any other code (either your code or 3rd party code) in the production org. – BarCotter Feb 24 '14 at 14:09
Currently i am changing the external css and pages code to redesign the application. So i need to test it again and again after saving and it is taking too much time to save a single comma or space or bunch of code. – Amit Agrawal Feb 24 '14 at 14:12
You should be doing all that testing in a sandbox rather than a production org. – BarCotter Feb 24 '14 at 14:13
Then you should be using a second sandbox to do this other development in. Never develop in production. There is no reason for it. – dphil Feb 24 '14 at 14:30

If you are only changing client-side resources for VF development, remember, you can reference those from anywhere. You shouldn't be inlining your JS or CSS anyway, so while you're fine-tuning, why not stick them in your own content server, edit them there, and then the refresh is immediate.

I've done this two ways.

One is to run a local static web server and reference it in my VF pages via localhost. This obviously only works if you are writing and testing on the same machine as the server. There was a good blog article on this in the developerforce blogs not too long ago.

The other is to serve static content from a public web server. I've typically done this with a heroku instance. There is a small lag while you push to your heroku repo, but nothing like waiting for your test code to run.


The reason we force you to run tests is so you don't screw up your production system! As has been said, all development should be done in a sandbox or developer edition org then pushed to production after thorough testing. So I would still suggest these techniques, but in reality you should be doing them in a system that is ring-fenced from your production org.

share|improve this answer

An alternative for small things such as CSS or javascript is to upload those files as static resources within salesforce. These are just files you upload to static resource records. Please take a look at the document here

Example Reference / Usage

share|improve this answer

There are also some third party tools that can help specific steps in this process. For example, it's a best practice to check the code of the production environment before you deploy to make sure there have not been any critical changes to the code in the production environment that could have an impact on your code. takes meta data snapshots over time so you can compare the code before you started the project and right before you deploy to make sure that it's sfae to deploy.

Additionally getting test data and refreshing the sandbox can slow down the entire process both during and between sprints/development cycles. They recently deployed a new tool that let's you replicate environments and the sync the full sandbox on your own schedule. This a lone can save a day or two of developer time.

share|improve this answer
Who is "they" that "recently deployed a new tool that lets you replicate environments and sync the full sandbox on your own schedule"? What's the name of the tool? Please provide details and links to support your post. You can use the edit button at lower left to update it. Thank you. – crmprogdev Mar 29 '15 at 17:11

Hurrey !!!! I got the solution to this problem.

You can save the pages , components , css etc through salesforce enviornment.

Here are the Steps -->

  1. Go to

  2. Type your creadentials and logged into the SF.

3.Click on the name top corner , right hand side and click setup option. develop , here all the static resources, components etc are listed .

  1. just click on any static resources, components click edit button there on the upper side.


Develop --> Pages --> --> edit -->(after changes)--> quick save --> save (finally)

it will not take too much time.

Note : For Apex Classes you need to change into Sandbox or Dev org after testing you can deploy onto server through eclipse and it will take time.

share|improve this answer
You can't directly edit most code directly in production. And even if you can, like with VF, you should still test in a sandbox and deploy to sanity check your work. – Andy Ognenoff Feb 25 '14 at 13:50
It is not possible to edit Apex classes in a production environment. The edit button is not there. You shouldn't be trying to do so in the first place. Develop in a sandbox and deploy to production. – Doug B Feb 25 '14 at 13:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.