Azure DevOps: 1 Solution Multiple Projects CI/CD

git visual-studio azure-devops azure-pipelines project-structure
RoLYroLLs picture RoLYroLLs · Mar 7, 2019 · Viewed 12.3k times · Source

I just started setting Azure DevOps with CI/CD. This might not be possible but I hope to find answers.

I have a solution with 6 projects:

  • Web Api project (references Infrastructure, Repositories, and Models projects)
  • Website project (calls the Web Api for data and references Infrastructure, Repositories, and Models projects)
  • Node.js project (only calls the Web Api for data)
  • Infrastructure project (shared by Web Api and Website)
  • Repositories project (shared by Web Api and Website)
  • Models project (shared by Web Api and Website)

Before I start searching on how to publish the Web Api, Website, and Node.js projects to their own Azure App Service within the CI/CD definitions:

Is it possible to set it up so that only certain projects are deployed? i.e.: the Node.js project is published only or only the Web Api and Website are published but not the Node.js.

Or do I need to keep things in different solutions?

If I keep them in separate solutions, how does this affect the shared projects (Infrastructure, Repo, and Models) in reference to Source Control (Git)? If I add code to the Models and Repo in the Web Api solution, do I commit these changes not he Web Api Git repo? How does this affect the other projects that reference the same Models and Repo projects? Is this where Git submodules come into play?

Update 1 (2019/3/8)

Looks like I might be able to get this working in 1 solution using Path filters (https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops). Still interested in any further input.

Answer

RoLYroLLs picture RoLYroLLs · Mar 13, 2019

Hoping this helps others:

I solved this by using Path filters on the Build definition and it works flawlessly. I have created 1 build definition per project that needs to live or be hosted somewhere (in my example, I have 3 Build definitions: Web Api, Website, Node.js).

With the proper path to the project in the Path filter only the proper Builds spin up, and any projects untouched do not trigger a build. Each build has it's own release which then deploys the specified app to it's own destination.

Related questions

Visual Studio 2017 - Git failed with a fatal error

I am using Visual Studio 2017 Community Edition (CE), and I have signed into my Microsoft account and I am connected to VSTS. I can see all my projects and repositories, but when I attempt to pull/fetch/push any changes …

Read More
What are the big differences between TFVC (TFS Version Control) and Git for source control when using Visual Studio 2013?

There are tons of questions and answers about Git versus TFVC Source Control, but no current answers cover the integration of Git into Team Foundation Server/Service that I can find. I'm starting green pasture development using a wide variety …

Read More
Change GIT account of Visual Studio Team Explorer

I am having a very weird situation when cloning a Git repository from our company private server. The repository is not anonymous (it requires authentication), but when cloning, VS didn't ask any username and password and automatically use an old …

Read More