10 months ago
We have Railway configured to create a PR environment for all new pull requests. However, very frequently, it fails to deploy the actual changed service in the PR environments it creates. An example is this PR: https://github.com/drips-network/app/pull/1502
As you can see, the message Railway left is missing the link to the app, which is because it wasn't deployed.
When I click on the non-deployed service and trigger a manual deploy by clicking "Deploy the repo drips-network/app", it displays an error "There was an error deploying from source." in the bottom right.
11 Replies
10 months ago
Hello,
Can you link directly to the service you have red circled?
same problem with https://github.com/drips-network/app/pull/1503 and https://github.com/drips-network/app/pull/1504
10 months ago
looks like we don't have workflow data for that old PR environment, I can leave this thread open, and can you let us know when you see this again?
Hey! looks like it might be related to # in the branch name
just opened two identical PRs except:
https://github.com/drips-network/events-processor/pull/55 has
#, fails to deployhttps://github.com/drips-network/events-processor/pull/54 doesn't have
#, deployed fine 1st try
10 months ago
would be kinda funny if we aren't escaping the hash in the url
10 months ago
is this reproducible? aka as long as the pr has a hash symbol, the pr environment will always fail every single time
it does seem to be yeah lol
did another test, here's one with #, again failed https://github.com/drips-network/app/pull/1510
and here the same PR without #, deployed OK https://github.com/drips-network/app/pull/1512
10 months ago
thats very interesting, seems reproducible, ill try to reproduce it myself and then ticket it!