Monorepo Support and/or filtering based on VCS changes in a specific directory | Cloud Feature Requests

CircleCI Ideas

Create

Home

Cloud Feature Requests

817

371

Monorepo Support and/or filtering based on VCS changes in a specific directory

under review

Jamie Talbot

Currently, any merges to master trigger all steps of all workflows. In an monorepo that houses multiple projects, this results in multiple redundant steps as, for example, the backend is re-tested and re-deployed even if only frontend changes have been made.
It is currently possible to do:
workflows:  flow:    jobs:      - deploy:          filters:            branches:              only:                - master
It would be useful for all teams that run a monorepo to also be able to specify, say:
workflows:  flow:    jobs:      - terraform:          filters:            modified_paths:              only:                - /^infrastructure/      - deploy:          requires: terraform          filters:             modified_paths:               only:                 - /^app/
CCI-I-208

February 4, 2018

Matthieu Adjogah

Something like the job below should work for monorepos: unit_tests: executor: terraform_image steps: - cache_restoration_for_job_to_job - run: name: Run unit test for the updated modules only command: | # We get the commit paths, and extract only the 2 first levels of each path for change in $(echo "$(git diff-tree --no-commit-id --name-only -r HEAD)" | cut -d/ -f 1-2); do # Then we check that a subfolder "examples/integration-test" exists under what we got if [ -d "${change}/examples/integration-test" ]; then terraform init "${change}/examples/integration-test" terraform validate "${change}/examples/integration-test" fi done

Abcs

Any updates please?

maor cycode

Any update?

Hyo Jang

Any updates?

Danny Nemer

Any updates?

Tim Kidd

This is the best solution I can find. Any update on this?https://github.com/labs42io/circleci-monorepo

Piers MacDonald

This is THE most requested feature and there hasn't been any progress in a year.

Rob Grant

We are definitely aware our monorepo support can be improved in various ways. A short-term fix will be to better surface information about the delta each trigger represents in terms of git SHAs. Longer-term, our plans are to allow more dynamic creation of config through inspection of the state of code. The idea is to give you power to do arbitrary work to then decide what the shape of your workflows should be. That work is currently sitting behind some other refactoring going on and finishing our roll out of pipelines for all projects.It's been a year since this. What's the update?

Roopak Venkatakrishnan

So after waiting a while, I ended up building this into my orb:Example github repo: https://github.com/roopakv/circle-monorepo-via-swissknifeorb command: https://circleci.com/orbs/registry/orb/roopakv/swissknife#commands-trigger-workflows-for-all-modified

Phillip Nielsen

I will most likely be moving at least some of our projects off of circleci and to github actions if this is not implemented or at least a timeline shared in the next few months. Definitely needed.

→