D365FO Code deployment process LCS & CI/CD pipeline

 Through Lifecycle Services (LCS)

Step 1:

Login to Azure DevOps https://dev.azure.com/XXXX and navigate to the pipelines -> Go to latest check-in, and click published (highlighted in yellow) as shown below. You can get the package from Artifacts location. 

Download the file that starts with AXDeployableRuntime***** 



Step 2: Login to LCS ( https://lcs.dynamics.com – Go to Asset Library  

 

Step 3:
Upload the code package by Clicking + button in Software deployable packages section of Asset Library  

Step 4:
Go to Environment details page ->Maintain-> Apply Updates  

Step 5:
Provide a unique name for the deployment and Select the code package that you have uploaded in step:3 and Click on “Apply” as shown here 


Step 6:
You can see the progress of the deployment and the time taken to apply the package depends on the no of steps as highlighted here. 

Through Azure DevOps: 


Step 1:

Login to Azure DevOps( https://dev.azure.com/XXXX) navigate to Pipelines-> Releases 

 

Select the Deployment to UAT pipeline and click on the “Create Release” to initiate the deployment manually. 

  

Note: Currently the Release pipeline is set to automatically trigger as soon as the completion of the Build pipeline. 

Step 2: Upon the successful run of the pipeline, the environment goes into servicing state. 

 

Environment will be available only after the environment status returns to Deployed state 

Note: You cannot delete the newly applied package in case of any issues, but you can regain the environment to the previous state by applying the previously applied package again. 

Step 3:

Redirect to the Pipelines section on the left pane

Select the Releases. 


Step 4:

 

 

  1. Here we have two pipelines which are created for the Code deployment to Tier 1(XXX-Test) and Tier 2(XXX- Acceptance) environments. 

  1. We have an option of automating the deployments as soon as the Build pipeline execution is completed.  

 


 

 

 

 

  1. For the code deployment pipelines, we have defined two predefined tasks in stage where one is to pick the latest generated package from artifact location and upload to the LCS Asset Library, the other task is to initiate the deployment to the environment. 

 


 

 

  1. In each task, we have provided the basic environmental details for the connection to set up between LCS and Azure DevOps through Service connection.  

 

  1. You can also trigger the release pipeline manually by choosing the Create Release button. 

 

  1. After the successful completion of the release pipeline, code deployment gets initiated in the LCS. 

 

















Comments

Popular posts from this blog

Cannot create a record in Locations (LogisticsLocation). Location ID: 000010222. The record already exists. D365F&O.