Skip to content
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

Closed
pfronczak opened this issue May 15, 2015 · 6 comments
Closed

Deploy to Server doesn't work for inactive server #33

pfronczak opened this issue May 15, 2015 · 6 comments

Comments

@pfronczak
Copy link

"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.

@pfronczak pfronczak changed the title Deploy to Server doesn't work for inactive sserver Deploy to Server doesn't work for inactive server May 15, 2015
@DrByrnes
Copy link

@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.)

@pfronczak
Copy link
Author

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.
Deploy to server indeed works if the target project is subscribed to metadata objects.

@xjsender
Copy link
Owner

@DrByrnes , thanks for your response for @pfronczak .

@DrByrnes
Copy link

My pleasure, @xjsender !

@xjsender
Copy link
Owner

@pfronczak , @DrByrnes , this is a bug, it will happen when target deployment org didn't describe_metadata.

@xjsender xjsender reopened this May 18, 2015
@xjsender
Copy link
Owner

This issue is fixed in the release 2.9.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants