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 4:
Go to Environment details page ->Maintain-> Apply Updates

Step 6:
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.
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
Here we have two pipelines which are created for the Code deployment to Tier 1(XXX-Test) and Tier 2(XXX- Acceptance) environments.
We have an option of automating the deployments as soon as the Build pipeline execution is completed.
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.
In each task, we have provided the basic environmental details for the connection to set up between LCS and Azure DevOps through Service connection.
You can also trigger the release pipeline manually by choosing the Create Release button.
After the successful completion of the release pipeline, code deployment gets initiated in the LCS.










Comments
Post a Comment