Using --filter in CI
#1582
-
|
Hello! First off, just getting started with it but love the tool, think it'll be heads above lerna. I am, however, having issues with the Here is output on my local machine of You can see that the Now here is output from my Drone CI pipeline. This is NOT working as expected. This is the same build as my local build, but it's not detecting the same diff/changes. You'll also notice in my Drone job I ran the So I only see the issue in my Drone CI pipeline. Didn't want to file an issue yet, because thinking I might be missing some configuration or something, but no idea where to start and couldn't find answers searching the repo (best I found is #1032 and #1079, but didn't seem quite the same). Any ideas where I might start to figure this out? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
Same here with turbo v1.4.7 and pnpm v7.12.2 |
Beta Was this translation helpful? Give feedback.
-
|
This looks like it could be a bug, can you open an issue instead of a discussion? |
Beta Was this translation helpful? Give feedback.
-
|
The issue is that you are passing
|
Beta Was this translation helpful? Give feedback.
-
|
Even better here.. Left(locally) is correctly identify 1 package changed since master.. right(ci) has same output all of the time |
Beta Was this translation helpful? Give feedback.
The issue is that you are passing
--filtertonpmon CI, and to Turborepo locally. You need an argument separator in there:npm run test -- --filter=[origin/main]