microsoft/azure-pipelines-yaml

Devops for Micro Service

cedrox opened this issue · 1 comments

I would like to have your inputs about a problematic that we encounter today and that seems to be quite common nowadays. Unfortunately, it seems also that there is no obvious solution…
We have a mono repo on azure devops and we try to stick to release branch convention. We need to deploy and release deployment Units / Workloads (netcore apis, nodejs api, workbook on synapse,…) without building and test it if there is no change…
The aim is to have :
- Modularization of the steps to allow a fined grained deployment and QA stages to run. (like terraform do plan apply, you could do a plan apply to your release 1.3 from 1.2 for example)
- Reuse built artifacts across environments to remove useless build phases.
- Avoid to build / deploy / Test everything if we have 2 lines of html change in a PR…
It seems that Bazel build can help here… Do you know any other reference implementation?

Hi @cedrox, thanks for reporting! We are working on more prioritized issues at the moment but will get back to this one soon.