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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Package exclusion from Build definition. (not PackagingExclution)

(0) ShareShare
ReportReport
Posted on by 30

Hi, 

I have Trunk/Main created from LCS autoupgrade tool. This is mapped to PackagesLocalDirectory in all DEV machines. In "CodeMergeSolution" I've created new Project and mapped it to custom package/model, where all the extensions will be created and objects moved to from upgrade models in OOB packages.

In CodeMergeSolution configuration properties (VisualStudio), I've removed check from Build property for all the packages except the new custom one, so developers could build application of what they've already upgraded (extensions, new objects etc.) excluding all the oob packages with upgrade models. Intention of that - is easier to work in one solution, by moving objects from upgrade models to custom one (just drag drop and build). 

Now I want to build a pipeline, which would took code from Trunk/Main, but would Built only one custom Package/model, excluding all the OOB ones (with many upgrade models - which would result to thousand of errors if were built). 

I see only one property in Build definitions - PackagingExclusions. But I need somethign as BuildExclusions? What is the other way to achieve this? How build pipeline decides which packages to build?

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

    If you go to your pipeline definition and open properties of "Get sources", you can modify the workspace mapping. Simply include just those packages that you want to build.

  • Verified answer
    Joris dG Profile Picture
    17,775 on at

    Have you considered using the hosted build pipeline? It's project based so you could just decide which project to build, like normal .NET development...

    docs.microsoft.com/.../hosted-build-automation

  • D365FOer Profile Picture
    30 on at

    Both solutions are good. Thanks Martin and Joris.

    With OOB Pipeline its much easier - as it comes automatically with Build machine deployment. (more cost of course)

    Hosted Buid is a bit complicated to set up + additionally requires to maintain nuget packages with new PU releases.

    One disadvantage I've noticed is that if I map only one model to build (oob pipeline) - only that model changes will be checked-in.

    Build pipeline for me mainly is required for gated check-in. So I can't check-in my custom model and all other upgrade model changes at once.

    I need to do two check ins. First check-in custom Package/model - which will go through gated check-in. And with second check-in - all other changes under Trunk/Main (usually CodeMergeSolution/UpgradedSolution project structure changes & also object deletions from upgrade models).

    Despite of that all works like a charm!

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…

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

#1
Martin Dráb Profile Picture

Martin Dráb 503 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

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

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 278 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans