Build server and Dev server (Tier1)in D365FO

(2) Share

Report

Posted on by CU05031448-0

1,275

Dear team,

Suppose I have DEV environment and I have created deployment package.

My query is how this deployment package is used by Build server to deploy in UAT.

Pls let me know the process happened in behind.

Thanks in advance!

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (12)

Answers (4)

Verified answer

Anthony Blake 2,905 Super User 2025 Season 2 on at

Like (1)

Report

Hi @CU05031448-0

A build server runs an agent, which is registered in Azure DevOps.

The flow you should look to target is:

Dev Server -> Check in code -> Azure DevOps Repo -> Azure DevOps pipeline (Build) -> Build Server -> Azure DevOps Artifact -> Azure DevOps Pipeline (Release) -> Deploy to Environment

There are details in each step which depend on the source control configuration (TFVC or Git), your pipeline configuration (Classic or YAML), the target environment (LCS or Power Platform), plus many more.

Have a really good read of the standard MS learn material here:https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/pipeline-create-deployable-package

And of this amazing website: https://ariste.info/dynamics365almguide/

Good luck.

Anthony

2 people found this reply helpful.

Was this reply helpful? Yes No
CU05031448-0 1,275 on at

Like (1)

Report

Thanks Anthony for the response.

As you said about the flow

"Dev Server -> Check in code -> Azure DevOps Repo -> Azure DevOps pipeline (Build) -> Build Server -> Azure DevOps Artifact -> Azure DevOps Pipeline (Release) -> Deploy to Environment"

From the DEV server, once I checked in the code it goes to

Azure DevOps pipeline(Build)

Now here I have one question --

We can create a deployment package manually or automatically.

One thing is not cleared in which steps it catch deployment package to proceed.

Where deployment package stored? Is it AOS Service - PackageLocalDirectory. ?

What does Azure DevOps Atifacts?

Kindly elaborate please.

Thanks in advance.

.

Was this reply helpful? Yes No
Verified answer

Anthony Blake 2,905 Super User 2025 Season 2 on at

Like (1)

Report

Hi @CU05031448-0

The build process, either via a hosted agent or a build server (choose hosted, its better!) should be configured to copy the package back to AzureDevops, and it will be stored as an artifact. The release process will upload this to LCS or Power Platform to be applied to the environment, depending on how your environments have been deployed. I would steer well clear of deploying packages generated in Visual Studio.

Anthony

2 people found this reply helpful.

Was this reply helpful? Yes No
CU05031448-0 1,275 on at

Like (1)

Report

Thanks Anthony,

As per my understanding,

In the step Azure DevOps pipeline (Build) - it took the Deployment package and stored in to Artifacts.

From the Artifacts , it took that package and further process it to Release it through Release pipeline. And upload it to LCS.

From the LCS, we used that deployment package to deploy it in to Target environment (UAT) through apply update.

Am I correct about the process?

Kindly validate please.

Thanks in advance.

Was this reply helpful? Yes No
Verified answer

Anthony Blake 2,905 Super User 2025 Season 2 on at

Like (1)

Report

Hi @CU05031448-0

Yes you have understood correctly, and what's even better, is that the deployment in LCS itself can also be automated using pipelines.

Thanks,

Anthony

2 people found this reply helpful.

Was this reply helpful? Yes No
CU05031448-0 1,275 on at

Like (0)

Report

Thanks Anthony for the update.

Only one thing ...

As I mentioned " the step Azure DevOps pipeline (Build) - it took the Deployment package and stored in to Artifacts."

Where we commonly get the Deployment package in application? I mean where it stored generally.

Kindly elaborate pls.

Thanks in advance.

Was this reply helpful? Yes No
CU05031448-0 1,275 on at

Like (1)

Report

Is it AOS/PackageLocalDirectory ?

Kindly confirm please.

Thanks!

Was this reply helpful? Yes No
Martin Dráb 237,722 Most Valuable Professional on at

Like (1)

Report

Deployable package isn't stored anywhere in the application. It's purpose is to deploy files; it's not needed after deployment.

Application files are indeed stored mainly in PackageLocalDirectory.

2 people found this reply helpful.

Was this reply helpful? Yes No
CU05031448-0 1,275 on at

Like (1)

Report

So, once Deployment package has been created. It will be in PackageLocalDirectory.

Right?

Was this reply helpful? Yes No
Anthony Blake 2,905 Super User 2025 Season 2 on at

Like (1)

Report

Hi @CU05031448-0

Well, not really. It depends entirely on your build pipeline and how it is configured, in most cases it would be deleted from the build server during a cleanup step after being stored in Azure DevOps. The build server its purely for building, take for example an Azure DevOps hosted build agent, your would never have access to the file system so there is no reason to store the package on it.

Have a look at the documentation and try it out, and if you encounter any problems, ask specific questions on the forum to gain help, there are a lot of community members with great ALM experience, they are sure to help.

Good luck,

Anthony

2 people found this reply helpful.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Build server and Dev server (Tier1)in D365FO

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

Build server and Dev server (Tier1)in D365FO

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates