I'm working with a Turborepo that contains three separate websites located in 'apps/web1', 'apps/web2', and 'apps/web3'. I'm trying to decide on the best CI/CD approach for this setup. Should I use a single pipeline that triggers deployments only for the apps that have changes, or should I go with separate pipelines for each website? For instance, if I update 'web1', I only want 'web1' to be deployed. What's the industry-standard practice for this situation?
1 Answer
I think you already know that having separate pipelines is the way to go here. Most CI providers let you run jobs only when specific files change, so you can set up separate jobs for each app and trigger them accordingly. That way, only the updated app gets deployed, keeping things efficient!
I get that, but I'm unsure about how to actually set this up. Can you share any articles or documentation that could guide me through the implementation?