web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Dev pipeline, Build Pi...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Dev pipeline, Build Pipeline and release Pipeline

(0) ShareShare
ReportReport
Posted on by kgh 80

Hi, 

I 'm trying to setup Azure DevOps project for our customer's Dynamics 365 FO Implementation project and configure it so that we can use it for Continues Integration and Continues Delivery.

We have 1 DEV (Cloud Hosted), 1 UAT (Sandbox : STANDARD ACCEPTANCE TEST) and we will soon have 1 PROD environement.

Currently we consider:

  • the UAT environment as Pre-Prod environment
  • the DEV environment as Test environment 

I have successfully created a DevOps Project and connect it to LCS project

then I created a Build server from LCS >> after deployment of Build server I found a repository as a trunk with main folder and a build pipeline.

I converted the Main folder  to a Main branch and then I creatd a Dev branch from the Main branch ( I did that from the Visual Studio in our VHD VM)

devops.PNG

and I intented to map the DevOps Dev Branch to "C:\AOSService\PackagesLocalDirectory" on our local VM and create a new DEV Pipeline, but I need to understand after check-in a my source code from the local VM to Dev branch , what are the next stpes to follow and how can I merge the Dev Branch to Main Branch ? and can I deploy the deployable package which will be generated later from Build Pipeline to a Dev environment (currently considered as Test environnement )?

The Dev Pipeline is considered to build the Dev Branch ? 

Thank You

I have the same question (0)
  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 237,965 Most Valuable Professional on at

    Please look at MSDyn365 & Azure DevOps ALM; you should be able to find many answers there.

    Regarding branches, thing again if you need multiple branches at the moment. It's good to start with a simple setup and add branches if needed. Having extra branches isn't for free, because you must spend time with merges. You can merge branches in Source Control Explorer; see Merge folders and files for details.

    Azure DevOps have no concept of a DEV pipeline. The build pipeline compiles source code and create a deployable package and the release pipeline takes the package and install it to an environment.

    Regarding your environments, if you use Dev as Test and you'll be deploying binaries there, you lack a Dev environment where you can write code to be deployed. Why don't you keep using Dev as Dev and use the User Acceptance Test (UAT) environment for testing of deployments?

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,162 Moderator on at

    As Martin pointed out, you also need a dev system that is used for the actual development. Actually you need one dev system for each developer.

    But, of course you can still use Cloud hosted environments as test systems, too. And you can deploy deployable packages to Cloud hosted systems. But development must be done in dedicated systems.

    I would also advice you to forget branches for now, until you have everything set up and working correctly. Once you are comfortable and familiar with the basics, you can branch a DEV branch from your MAIN branch and start doing development in DEV branch.

    When you do that, you usually need one more dev system for maintaining MAIN branch (=merging code from DEV to MAIN), since you need a system where the PackagesLocalDirectory folder is mapped against MAIN branch. Switching between different branches in one dev system is quite slow and cumbersome. MS is working on enhancements in this area, though.

  • kgh Profile Picture
    kgh 80 on at

    Thank you Martin and Nikolaos

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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

#1
Martin Dráb Profile Picture

Martin Dráb 451 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 428 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 239 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans