You need to sign in to do that
Don't have an account?
wsuycott
Eclipse deployment headaches - multiple classes/triggers
Have already deployed from eclipse projects successfully into one of several production orgs. In my current sandbox org and eclipse project I have 1 trigger and 1 class that are already deployed to production, and have created another trigger and another class that when tested in sandbox show 100% code coverage. When running the tests in Eclipse however one time it will show that one class/trigger tested fine and the other class/trigger failed. I resave these and run the test in Eclipse again, and this time the previously failed class/trigger are now ok and the former ok class/trigger are failing. Because one element fails the attempt to deploy - even if I am only attempting to deploy the class/trigger that passed the test ends up failing.
As the documentation on the entire Eclipse/Force development is slight there is no real cookbook approach that I have thus far found to help support what will be an on-going environment wherein developers will have an increasing number of classes/triggers that were developed OR some that are still in a state of development that aren't ready to deploy - and all of them impacting(preventing) the deployment of a class/trigger that IS ready for deployment. It is impacting my productivity and frankly I have burned a good 20 hours now trying to get well covered code out of my sandbox and into production.
Any tips on how to handle this????
Also, are you using the "Deploy to Server" wizard from within a project that is otherwise pointing at your Sandbox? Or have you created a project directly against your production org?
Thanks,
Jon