4 months ago
I’m using Railway with three environments: staging, prod, and main, each connected to its respective Git branch.
Today I noticed something odd: when I pushed changes to the main branch, all components across environments started building again, even though nothing was merged into staging. I was expecting only the components tied to main to rebuild.
Is this expected behavior with Railway’s environment–branch mapping, or could something be misconfigured in my setup?
If this approach isn’t ideal, what’s the recommended best practice for managing multi-environment deployments with Railway?
Also, slightly unrelated, are there any plans to support tags/releases for deployments in the near future?
Would love to understand what’s going on here. Thanks!
7 Replies
4 months ago
Can I get a link to the project?
4 months ago
So I am looking at the webserver service in your production environment, that service deploys from your release branch.
And its most recent deployment was caused by you changing an environment variable, not by any kind of Github push.
So I am really not seeing any evidence for what you are saying is happening.
The staging was getting rebuilt and in the title it was showing, the latest commit that was merged into main
Let me provide you more evidence, I might need to send some confidential screenshots. Is there any way of making this thread private .