-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Path Filtering Orb Doesn't Detect Changes #102
Comments
Just did some more testing, it looks like the issue is related to the mapping itself. cloud-dev/.* trigger-cloud-dev-dir-01-route53 true And it worked, however I want to trigger the workflow only when there are changes within cloud-dev/01_route53/.* Any ideas? |
I think I found a solution config.yml
continue_config_cloud_dev.yml:
It turns out also the default directory of the instance was changed from /home/circleci to /root I have no idea why as I was using the same image. |
Orb version:
pathfiltering orb version 1.0.0
What happened:
Hello,
I am experiencing issue with the path-filtering orb.
The default parameters for triggering a workflow are set to false in the continue_config, and in the config they are set to true, however the changes within the directories are not detected and the parameter doesn’t change its value to true.
I’ve tried correcting the mapping paths based on the exact directory that the code is located in the circleci istance that is being used during deploy but without success.
Weird part is I have another repo with 99% similar configuration that is working as expected.
I have created a separate branch from the one that I am working on so from feature/KI-10 to feature/KI-10-pipe-test just to make sure that it will do the base-revision based on the changes between the KI-10 and KI-10-pipe-test branch.
I also testeed the base-revision to branch withiut the "/" symbol as suggested here: https://discuss.circleci.com/t/path-filtering-orb-not-triggering-workflows/50517
I've tried with a lot of different configurations, however the simpliest one is this:
config.yml:
continue_config.yml:
Example from one of the many tries:
https://app.circleci.com/pipelines/bitbucket/kadanza/kadanza-saas-infra/2706/workflows/04a0e9a8-14aa-4096-a319-51f7292f4bdf/jobs/2430
Expected behavior:
The goal is to trigger the workflows if changes are detected within the specified directories.
Additional Information:
Any advices are highly welcome, as I am struggling to find a solution for a couple of days now, thank you!
The text was updated successfully, but these errors were encountered: