How do I keep deploys from being broken by Railway "auto" rollouts?
kineticac
HOBBYOP

3 months ago

We're constantly fighting random rollouts that break our deploys, specifically our watch paths. We have so many "skipped" deploys because they broke something with watch paths in railway.json files, and then again recently with metal builds turning on and completely skipping every deployment. This is so unacceptable. How can we avoid these kind of problems in the future, or is this just how Railway works?

Closed

6 Replies

3 months ago

What's your watch path set to?


3 months ago

to answer your underlying question though, no, you cannot opt out of Railway updates. Although Railway does keep new experimental features separated as feature flags which you can enable or disable in your account settings


kineticac
HOBBYOP

3 months ago

@Fragly It's for our frontend service. It was in our railway.json which worked great for awhile, then a couple months ago that stopped working and we had to move it into the hardcoded settings in the railway interface. And THEN the metal build doesn't interpret these correctly and just skips everything anyway

src/**
public/**
scripts/**
index.html
package.json
package-lock.json
.npmrc
Dockerfile
vite.config.js
tsconfig.json
!backend/**```

kineticac
HOBBYOP

3 months ago

It's crazy they pushed us to use that metal build automatically, knowing it would break the watch paths. That kind of thing just can't happen.


3 months ago

interesting, thanks for explaining


sam-a
EMPLOYEE

3 months ago

Responded in your other thread.


Status changed to Closed sam-a 3 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...