Not skipping build/deployment for changes outside root directory
I have a monorepo setup, where I have a folder called
apps that contains different services. I have separate deployments in my railway project, each using a subfolder as their root directory (e.g. /apps/server). Currently there are two subfolders/services. I just pushed a new folder to the apps directory (which is not even connected to any service in the project yet), and it triggered a build and deployment for the two existing services.
That is not supposed to happen right? Is there something else I need to configure so that I only trigger new builds for apps that have changes to the root directory?7 Replies
Project ID:
22710f9c-32c2-47ea-ba96-303b0801e10e22710f9c-32c2-47ea-ba96-303b0801e10e
I also noticed this, wondered if I had done something wrong.. a workaround I found was to use the Watch Paths https://docs.railway.app/guides/build-configuration#configure-watch-paths
But this seems like it shouldn't be needed after setting the root directory of each service. So very interested in what the solution is!
neither of you are doing anything wrong, I have let the team know about it in previous help threads, but no action taken yet
Ah, so it's a known issue. Should I mark this post as solved then?
hold off on that, i will ping a team member tomorrow
team is aware of this issue and will be working on it when possible
Thanks @Brody ! Using watch paths of course solves the issue as well, so I guess it's more about expectations/inconsistent docs than actually a blocker/problem.