Multiple Projects and One Solution - DevOps Best Practice

0 votes

For example, I have one solution and multiple projects. The multiple projects are:

  • Solution
    • REST API Web Application
    • Admin UI Web Application
    • Shared Libraries

To have an Azure DevOps pipeline for the REST API and the Admin UI, what would be the best approach?

  1. If anything changed in the solution, trigger build for everything and deploy BOTH web apps
  2. CI / CD triggers for each deployable project; ie. if only UI change in Admin UI, then only build for that happens

I like #2. I am thinking that if only REST API changes, then only REST API will trigger CI / CD for itself. If Admin UI changes, only CI / CD for it triggers. If Shared Libraries is changed, both CI / CD triggers.

I believe this can be done using Path Filters as the trigger. However, what if in the future I have a new Shared Library2? I would need to edit the Pipeline trigger for that new project. So I am not sure anymore if this is good practice.

Mar 22, 2022 in Other DevOps Questions by Kichu
• 19,050 points
2,436 views

No answer to this question. Be the first to respond.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.

Related Questions In Other DevOps Questions

0 votes
0 answers
0 votes
1 answer
0 votes
1 answer
0 votes
1 answer
0 votes
0 answers

OWASP Zed Attack Proxy Scan in DevOps pipeline

I want to do the "Authenticated Scan" ...READ MORE

Mar 15, 2022 in DevOps Tools by Kichu
• 19,050 points
687 views
0 votes
1 answer
0 votes
0 answers

Multiple YAML build pipelines in Azure DevOps

Using the new YAML way I want ...READ MORE

Mar 15, 2022 in DevOps Tools by Kichu
• 19,050 points
948 views
webinar REGISTER FOR FREE WEBINAR X
REGISTER NOW
webinar_success Thank you for registering Join Edureka Meetup community for 100+ Free Webinars each month JOIN MEETUP GROUP