It is my understanding that we only track one watch path per service, but let me confirm this to be the case and attempt a re-production.

When specified, any changes that don't match the patterns will skip creating a new deployment. Multiple patterns can be combined, one per line.

I saw this in the documentation; not sure if I am doing something wrong?

Okay- I wasn't able to repro esp. with multiple watch paths, can you disconnect and reconnect your GH for me? If I had to guess, your GH auth token exp. and didn't read the webhook.

Tried a few things... it seems like the issue is when the watch path doesn't match the root directory I set in the "Source" section in Railway config rather than because there is multiple.

When pushing a change to apps/backend -

root=apps/backend + watch=apps/backend = works

root=apps/tika + watch=apps/backend, apps/tika = does not work

root=apps/tika + watch=apps/backend = does not work

root=apps/tika + watch=(empty) = works

Gotcha, I think on it's face makes sense, for most monorepos, we assumed that we wanted to deploy when the root changes, but it seems like you need the rest of the services to rebuild, is that correct?

Yes, I want the services to rebuild if certain directories have changes (which may be outside of their root). It does trigger deploys if I delete the watch path entirely though.

The docs seemed to say this was supported?

Note, if a Root Directory is provided, patterns still operate from /. For a root directory of /app, /app/**.js would be used as a pattern to match files in the new root.

Dumb suggestion here, have you tried adding the leading slash?

`apps/tika` vs `/apps/tika

Smart suggestion I think I did try both - got the same "Skipped" message below with or without the /

Okay- noted, going to raise a ticket on our side. Can you tell me how burning this issue is so that I can prioritize it to the team?

Thank you! It's not a hard blocker for us but definitely super annoying to have to choose between everything redeploying when there's only frontend changes in our mono repo vs. having to manually deploy :(

Still observing this behavior as well? (We might think we found something that is related.)

yes just did a deploy and it skipped the same services

Hi! Just checking if there was any update on this

An internal ticket has been attached to this thread. Updates will be relayed in this thread, so keep an eye out!

Hey there Truffle,

We've been having difficulties re-producing this issue, however, there is a related ticket that should address what we think is the source of the problem. It's logged for engineering. Our support tool will give you updates as that ticket moves along in the process.

Thanks,
Angelo

Update: An internal ticket linked to this thread has been changed to Todo.

Update: An internal ticket linked to this thread has been changed to Backlog.

Hey Truffle,

Just wanna update you on what that above message means, similar to what Angelo had said previously, we haven't been able to reproduce it, and we have not seen any influx of users reporting the same thing, so this has been moved into the backlog until we are provided fully reproducible steps.

Best,
Brody

@brody - Hi, I've shared a Github repo to reproduce this issue here: https://github.com/TruffleClock/deploy-bug-repro along with instructions in the readme.

I'm able to consistently repro the issue with this simple codebase.

I have also created a project 3ff50838-9b45-4ae3-8b4b-8bf092e0790b on Railway that the team can look at to see the issue.

Let me know if this helps or if there's any other info I can share to help them repro the issue!

Can you try -

apps/backend/**/*

and -

apps/backend/**/*
apps/tika/**/*

nope, same issue

You also have the root directory set to apps/tika

I'm fairly certain that means only files changed in the root directory will be deployed, regardless of what you have set in the watch paths.

nope, if i remove the watch paths, both services deploy when apps/backend is changed. just testing this again on the new test repo to verify, and it worked.

in the docs for watch paths (https://docs.railway.com/guides/build-configuration#configure-watch-paths), it says this:

Note, if a Root Directory is provided, patterns still operate from /. For a root directory of /app, /app/**.js would be used as a pattern to match files in the new root.

i thought this would mean that paths outside of the root directory for a service should still be valid?

Honestly, at this point, it's not clear what the behavior you expect is, can you define that for me?

I expected that if I set the watch paths for a service to:

apps/dir1/**
apps/dir2/**

then that service would redeploy if there are changes in either directory

Update- we have the Linear attached, still waiting on engineering action.

❌ The ticket Deployment configuration issue has been marked as canceled.