# Codefresh Registry Trigger **URL:** \ **Category:** Pipeline Triggers\ **Created:** [November 22, 2019, 4:45pm UTC](https://community.codefresh.io/t/codefresh-registry-trigger/241 "2019-11-22T16:45:03Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Carlangueitor](https://sea1.discourse-cdn.com/flex019/user_avatar/community.codefresh.io/carlangueitor/32/66_2.png) [@Carlangueitor](https://community.codefresh.io/u/Carlangueitor)\ **Post date:** [November 22, 2019, 4:45pm UTC](https://community.codefresh.io/t/codefresh-registry-trigger/241/1 "2019-11-22T16:45:03Z")
Pipelines support some Docker registries as a trigger, but not the Codefresh Registry, it would be great to have it available. In my case, I have a project which is used to generate some files in other projects, and a way to keep those files updated is by updating it in a pipeline triggered once a new version is released. What do you think about it? ---
**Author:** ![Kostis](https://sea1.discourse-cdn.com/flex019/user_avatar/community.codefresh.io/kostis/32/391_2.png) [@Kostis](https://community.codefresh.io/u/Kostis)\ **Post date:** [November 25, 2019, 9:13am UTC](https://community.codefresh.io/t/codefresh-registry-trigger/241/2 "2019-11-25T09:13:12Z")
Hello and welcome to Codefresh community! While we have in our backlog the trigger from the Codefresh registry, a much better approach is to have the upstream job automatically trigger the downstream ones. This can be easily done with the [codefresh run step](https://codefresh.io/steps/step/codefresh-run). We have in our docs a complete example [with a parent and child pipelines](https://codefresh.io/docs/docs/yaml-examples/examples/call-child-pipelines/). For a real example you can also read the blog post on how we develop [Codefresh on Codefresh](https://codefresh.io/continuous-deployment/ci-cd-pipelines-microservices/) managing 25+ microservices with just two pipelines. The CI pipeline is just calling the CD one. Would this pattern work in your case?