Not skipping build/deployment for changes outside root directory | Railway | Page 1

mossy rose Jan 7, 2024, 9:12 PM

#

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?

little knotBOT Jan 7, 2024, 9:12 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

radiant loomBOT Jan 7, 2024, 9:12 PM

#

Project ID: 22710f9c-32c2-47ea-ba96-303b0801e10e

mossy rose Jan 7, 2024, 9:12 PM

#

22710f9c-32c2-47ea-ba96-303b0801e10e

crimson vessel Jan 7, 2024, 9:35 PM

#

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!

Railway Docs

Build Configuration | Railway Docs

Documentation for Railway

fallen flare Jan 7, 2024, 10:03 PM

#

neither of you are doing anything wrong, I have let the team know about it in previous help threads, but no action taken yet

mossy rose Jan 7, 2024, 10:37 PM

#

Ah, so it's a known issue. Should I mark this post as solved then?

fallen flare Jan 7, 2024, 10:38 PM

#

hold off on that, i will ping a team member tomorrow

fallen flare Jan 10, 2024, 6:06 AM

#

team is aware of this issue and will be working on it when possible

#Not skipping build/deployment for changes outside root directory