How Can We Manage Multiple Next.js releases in a Single Monorepo Using Turborepo, Docker, and Azure Pipelines? #10146
alamenai
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
I originally developed a Next.js application called app-1.
Later, my manager requested a second, smaller application called app-2, which uses Puppeteer in the backend.
To avoid juggling multiple repositories (especially since both applications run on Next.js), I transitioned to a monorepo architecture using Turborepo.
We use GitFlow for release management and Docker alongside Azure Pipelines for deployment.
Recently, my teammate made updates to app-1 and I made updates to app-2 and merged them into the dev branch.
When my manager asked me to release app-2, the CI/CD pipeline ended up building and deploying the entire monorepo—including app-1—because Turborepo treats everything as one project.
As a result, the final release included changes from both app-1 and app-2, even though we intended to deploy only app-2.
What's your suggestions on that?
Thank you
Beta Was this translation helpful? Give feedback.
All reactions