3 ms·
> Pipelines taking way too long. Build, test, and deploy cycles growing linearly with the size of the codebase. Gitlab CI config files have a "changes" stanza
by RedShift1 5y ago
> Pipelines taking way too long. Build, test, and deploy cycles growing linearly with the size of the codebase.
Gitlab CI config files have a "changes" stanza to limit which pipelines run, so that when you make a change in one part it doesn't run the entire codebase through CI and only releases that component. I'm sure other CI systems have similar controls, so by using that, this should be a non issue?
- victorNicollet 5y agoWe are using TeamCity for CI, which also supports triggers conditional on paths. It mostly works, as long as your tree is laid out properly.