-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy to Server doesn't work for inactive server #33
Comments
@pfronczak , make sure the inactive project is properly subscribing to the metadata objects. Switch to the target project, cache --> clear session cache, then settings --> toggle metadata objects. (Do this twice. The first time it'll pull down the list, the second it'll prompt you to choose.) Once you've subscribed and refreshed that project you should have no problem deploying to it from another active project. (I used this feature multiple times yesterday and it worked perfectly once all my projects were properly configured for the new metadata change.) |
Thank you - that did solve the problem. I never used this feature (toggle metadata) before - I was just creating package.xml's and refreshing projects. |
@DrByrnes , thanks for your response for @pfronczak . |
My pleasure, @xjsender ! |
@pfronczak , @DrByrnes , this is a bug, it will happen when target deployment org didn't describe_metadata. |
This issue is fixed in the release 2.9.6 |
"Deploy to Server" option doesn't work anymore when other than current (active) project is selected as a target for deployment. Selecting target server switches the active project but does not run the deployment.
I believe this stopped working some time around introducing changes with automatic opening of sublime projects when switching active project.
The text was updated successfully, but these errors were encountered: