{"id":943,"date":"2014-07-08T01:47:00","date_gmt":"2014-07-08T01:47:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2014\/07\/08\/how-to-trigger-deployments-to-chef-managed-environments-from-release-management-2013-with-update-3-rc\/"},"modified":"2019-02-14T17:48:09","modified_gmt":"2019-02-15T01:48:09","slug":"how-to-trigger-deployments-to-chef-managed-environments-from-release-management-2013-with-update-3-rc","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/how-to-trigger-deployments-to-chef-managed-environments-from-release-management-2013-with-update-3-rc\/","title":{"rendered":"How to trigger deployments to Chef managed environments from Release Management 2013 with Update 3 RC"},"content":{"rendered":"

    <\/span><\/span><\/span><\/span><\/p>\n

Pre-requisites for triggering Chef deployments using RM:
<\/span><\/span><\/span><\/strong><\/p>\n

    \n
  1. \n
    Target node must already be bootstrapped and registered with Chef server<\/span><\/span><\/span><\/span><\/div>\n<\/li>\n
  2. \n
    Relevant cookbooks uploaded to Chef Server. Cookbook should have an attribute which maps to build drop location.<\/span><\/span><\/span><\/span><\/div>\n<\/li>\n
  3. \n
    Recipes assigned to Node.<\/span><\/span><\/span><\/span><\/div>\n<\/li>\n<\/ol>\n

    Deployment using Chef:<\/span><\/strong><\/p>\n

      \n
    1. \n
       As a first step you need to setup Release Management Server as Chef Workstation. Refer to <\/span>Setting up Chef Environment<\/span>. <\/a><\/span><\/span><\/span><\/span><\/div>\n
        \n
      1. \n
        RM uses Knife<\/em> tool to communicate with Chef. If Knife windows plugin<\/em> is not yet installed, run the following command:<\/span><\/span><\/div>\n