Skip to content

Latest commit

 

History

History
48 lines (39 loc) · 3.75 KB

deploy.md

File metadata and controls

48 lines (39 loc) · 3.75 KB
Raw

Deploy

There has a setting switch_back_after_migration to control whether switch back to original project after deploy is finished, default value is true

  • Deploy Package Zip Step by Step, demo is here

    • Click HaoIDE > Metadata Migration > Deploy Package.zip in the main menu
    • Input your zip file path and click Enter
    • Waiting and checking the progress message in the output panel
    • After operation is finished, you will see the deploy result

  • Refresh Folders Step by Step

    • Choose the folders to refresh in the side bar
    • Click ```HaoIDE > Refresh Folder`` in the sidebar menu
    • Waiting for operation is finished until retrieve is finished

  • Deploy Files to Server Step by Step

    • Choose the files to deploy in the sidebar menu or context menu
    • Click HaoIDE > Deploy File to Server in the context menu
    • Choose the target organization to deploy chosen files
    • Waiting and checking the progress message in the output panel
    • After operation is finished, you will see the deploy result

  • Deploy Open Files Step by Step

    • Sometimes, when you want to deploy class, page or somethings else, however, you didn't want to choose them in the sidebar when there are huge number of code files, you can open the files that you want to deploy to server and Click HaoIDE > Metadata Migration > Deploy Open Files in the main menu to deploy multiply files to target server.

    • Actually, you can even open code files in different orgs and deploy them to the same org, for example, there have three classes to be deployed, A and B are in UAT environment and they are newly developed feature, C in UAT environment is completely different with production environment and there is urgent bug needed to be fixed in production, so at this moment, you can open A and B classes in UAT and the fixed version of C class in production and click Deploy Open Files to deploy the three class from different orgs to production environment.

    • This command is just enabled when any one of open files is salesforce code files.

  • Deploy Package Folder Step by Step, demo is here, if you just want to run specified test, you can change your testLevel in the deploy_options setting.

    • Choose a valid package folder, for example, src folder or Project/src, plugin will check whether src folder contains package.xml file, if yes, you will Deploy To Server command in the sidebar menu, otherwise, Deploy To Server will be hidden
    • Click the ```Deploy To Server`` command
    • Waiting and checking the progress message in the output panel
    • After operation is finished, you will see the deploy result

  • Deploy and destruct files at same time

    • There is a file_exclude_patterns in the default settings, which is used to hide file in the sidebar, remove the "*.*-meta.xml" from it and paste this setting to your User Settings
    • After file_exclude_patterns is changed, click HaoIDE > Update > Update Project Pattern, and then you will see the *-meta.xml files in the sidebar.
    • If you want to delete a class or trigger, you just need to update the *.-meta.xml file as below,
    <?xml version="1.0" encoding="UTF-8"?>
<ApexTrigger xmlns="http://soap.sforce.com/2006/04/metadata">
    <apiVersion>32.0</apiVersion>
    <status>deleted</status>
</ApexTrigger>
    • Choose the file to delete, update or created into other org and click HaoIDE > Deploy Files To Server
    • After deploy is finished, you will see the result.