Hi, I added renovate to my repo and I want railway to deploy so I enabled bot PR environments.However when renovate created a PR, railway created an environment for it but I can see a few problems:No deploys for some services, eg. postgres is fine but my custom apps are notSettings are not inherited. If I check the settings of the api app, no custom settings in there although I have some in the production environment.This seems specific to bot PRs because regular PRs work just fine

Bot PR environment doesn't copy settings properly nor deploys

florian-lefebvre

HOBBYOP

3 months ago

Hi, I added renovate to my repo and I want railway to deploy so I enabled bot PR environments.

However when renovate created a PR, railway created an environment for it but I can see a few problems:

No deploys for some services, eg. postgres is fine but my custom apps are not
Settings are not inherited. If I check the settings of the api app, no custom settings in there although I have some in the production environment.

This seems specific to bot PRs because regular PRs work just fine

Solved

12 Replies

Railway

BOT

3 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!

Railway

BOT

3 months ago

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

ray-chen

EMPLOYEE

3 months ago

Thanks for flagging this, we'll have a look

Status changed to Awaiting User Response Railway • 3 months ago

florian-lefebvre

HOBBYOP

3 months ago

Interesting, renovate force pushed to the branch and now the pr environment picked up all settings and attempted to deploy correctly

Status changed to Awaiting Railway Response Railway • 3 months ago

ray-chen

EMPLOYEE

3 months ago

Is this consistently reproducible with all renovate PRs? I'm wondering if what you saw was a blip in our processing queue

Status changed to Awaiting User Response Railway • 3 months ago

florian-lefebvre

HOBBYOP

3 months ago

I forced renovate to create a new pr and I confirm I can reproduce

Status changed to Awaiting Railway Response Railway • 3 months ago

ray-chen

EMPLOYEE

3 months ago

But a force push works? That is strange. Thanks for confirming!

Status changed to Awaiting User Response Railway • 3 months ago

florian-lefebvre

HOBBYOP

3 months ago

My theory is it doesn't manage to pick the very first commit but anything after is probably fine

Status changed to Awaiting Railway Response Railway • 3 months ago

Railway

BOT

3 months ago

Hello!

We've escalated your issue to our engineering team.

We aim to provide an update within 1 business day.

Please reply to this thread if you have any questions!

Status changed to Awaiting User Response Railway • 3 months ago

Railway

BOT

3 months ago

🛠️ The ticket Deployment Issue in Bot Environment has been marked as todo.

Railway

BOT

3 months ago

🛠️ The ticket Deployment Issue in Bot Environment has been marked as triage.

Railway

BOT

3 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 3 months ago

echohack

EMPLOYEE

3 months ago

Hey there! Can you try again? I think we've solved the issue!

Status changed to Awaiting User Response Railway • 3 months ago

florian-lefebvre

HOBBYOP

3 months ago

Yes it's solved thanks!

Status changed to Awaiting Railway Response Railway • 3 months ago

Status changed to Solved florian-lefebvre • 3 months ago