Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Devops for Micro Service #581

Open
cedrox opened this issue Jan 4, 2023 · 1 comment
Open

Devops for Micro Service #581

cedrox opened this issue Jan 4, 2023 · 1 comment

Comments

@cedrox
Copy link

cedrox commented Jan 4, 2023

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?

@kirill-ivlev
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants