PLEASE HELP

sarahsimionescu
FREE

3 months ago

I need a CI/CD pipeline so that

  • every PR, it will attempt to deploy it: if it deploys yay! if it doesn't rip. (super simple)

  • it was have a separate deployment for each PR

That's all. However, it seems like you can't use a project token to create a new environment or service, so is this impossible? Can I only reploy to that same, specified service?

I am so lost please help.

Solved

4 Replies

sarahsimionescu
FREE

3 months ago

ps I know there is like a Github App integration, but I think we have too many PRs or something because it will randomly just, not deploy, (probs cz we are hitting some limit). There are no error messages, it just says its deploying forever (but Railway never actually created the environment or deploys the thing). Therefore, we wanted to create a github action to handle this.


There is this feature

1366571410201510000


But it literally just seems to not function whatsoever


echohack
EMPLOYEE

3 months ago

@elverly @Loudbook Hey yall, we've been taking a deeper look here and this is a tough cookie to solve.

Can you give us as much information as possible? The best is a link to an environment that is in the "deploying forever" state. Any steps you have to reproduce would help.


I've never gotten an environment that is deploying forever. Nothing happens when a PR is created. It's like it doesn't even know it happened.


echohack
EMPLOYEE

3 months ago

oh it doesn't even create the environment at all?



sarahsimionescu
FREE

3 months ago

Yes absolutely.

  • sometimes, the environement will not create on railway

  • github will show it as "in progress" forever


sarahsimionescu
FREE

3 months ago

Actually, feel free to dm me we can re-create the issue and debug live


sarahsimionescu
FREE

3 months ago

let me think of more details I can provide


Wait, do you even get Railway to make a presence on your repo?


I see no indication Railway is present on my PR


sarahsimionescu
FREE

3 months ago

Well, it is a required check


And the app is installed and active on all repos

1366873040851439600


sarahsimionescu
FREE

3 months ago

for this branch according to the branch rules


sarahsimionescu
FREE

3 months ago

so I think it may be the case that it shows up as "in progress" by default if it is required


echohack
EMPLOYEE

3 months ago

Do your environments have volumes on them and are you using METAL_VOLUME_CREATION feature flag?


Railway didn't even make a check for me


Wait a second


echohack
EMPLOYEE

3 months ago

Just confirming something, we might have a fix in flight


sarahsimionescu
FREE

3 months ago

I only have one service, that being my next.js server. Not sure what that flag is, so I will assume no.


echohack
EMPLOYEE

3 months ago

OK I think your issue is different than Loudbook's


sarahsimionescu
FREE

3 months ago

I have

  • one service

  • one docker file (it will identify the docker file and use it to deploy)



And my issue isn't real


Because I'm an idiot


sarahsimionescu
FREE

3 months ago

Yes, it seems like it works for me some of the time


sarahsimionescu
FREE

3 months ago

but not all of the time


I had a bunch of GHCR containers but no actual "repo service"


So Railway has no idea what repo to be checking


echohack
EMPLOYEE

3 months ago

In life, being an idiot is eventually consistent <:LUL:462678129551474688>


very sad


echohack
EMPLOYEE

3 months ago

I have been there, no worries <:salute:1137099685417451530>


sarahsimionescu
FREE

3 months ago

Ok so new insight: I remove it as a required check, now, I can see that it doesn't even show up under "checks in progress" for those PRs for which it doesn't run…


sarahsimionescu
FREE

3 months ago

Even though it should, very confused.


echohack
EMPLOYEE

3 months ago

I need to swap back to the issue at hand, can I come back to debugging your issue elverly?


sarahsimionescu
FREE

3 months ago

For sure


echohack
EMPLOYEE

3 months ago

!remind me to come back to help elverly in 5 hours


sarahsimionescu
FREE

3 months ago

Do you have time?


sarahsimionescu
FREE

3 months ago

We can reschedule for anytime tomorrow (im EST)


echohack
EMPLOYEE

3 months ago

@elverly We can look at your Project and see if we can find something wrong


echohack
EMPLOYEE

3 months ago

@Brody will help you out from here. Apologies for the slow response, it's been quite busy 🙏


sarahsimionescu
FREE

3 months ago

No worries, yes let me know if i've configured anything incorrectly on my end! Otherwise feel free to book in a debug session anytime 9am-9pm EST


echohack
EMPLOYEE

3 months ago

!t


echohack
EMPLOYEE

3 months ago

This thread has been escalated to the Railway team.

Status changed to Awaiting Railway Response echohack 3 months ago


echohack
EMPLOYEE

3 months ago

Oh umm, is your Railway account different than this one? I'm not seeing any projects


echohack
EMPLOYEE

3 months ago

@elverly Ping me in the morning


3 months ago

We belive this is the project in question -

And if so, I am not seeing any PR environment that failed to get created, I am only seeing failed deployments, is that perhaps what you mean?


sarahsimionescu
FREE

3 months ago

Hello! Yes sorry the account I am concerned about is for a team I am part of. https://railway.com/project/c6887503-f14d-483f-9c0d-30ebf2700de7


sarahsimionescu
FREE

3 months ago

The major point of concern is that a lot of the PRs created do not end up being created as a PR environment in Railway, which means we cannot reliably use it as a required deployment check in our CI/CD pipeline.


sarahsimionescu
FREE

3 months ago

Which PRs become railway environments and which don't, is kind of difficult to tell. I feel like the only pattern i've noticed is that, since we are using https://graphite.dev/ it is common for us to push multiple PRs one after the other very quickly (as this is done in an automated way)


sarahsimionescu
FREE

3 months ago

@Brody @echohack ^


sarahsimionescu
FREE

3 months ago

Happy to recreate the issue, i'll be online all day just ping me.


3 months ago

do you happen to have a ballpark of how many prs you open in an hour?


sarahsimionescu
FREE

3 months ago

like 7


sarahsimionescu
FREE

3 months ago

could be opened in like 30 seconds


sarahsimionescu
FREE

3 months ago

is like the average


3 months ago

7 in 30 seconds?


sarahsimionescu
FREE

3 months ago

yep


echohack
EMPLOYEE

3 months ago

Sorry for the late reply here (it's been a busy day). I think the Graphite PR-stacking use case isn't supported well at this time. Are yall just starting out on Graphite or is this more of a bread-and-butter thing about how yall work?


Status changed to Awaiting User Response railway[bot] 3 months ago


sarahsimionescu
FREE

2 months ago

It is the bread and butter of how we work. It's just wraps over GitHub, so it's not really like an integration constraint, more of a performance one. (Not sure how it's implemented on your end but,) If GitHub pings you with "New PR Created" events, one after the other, I need to ensure that Railway will pick them up.


Status changed to Awaiting Railway Response railway[bot] 3 months ago


sarahsimionescu
FREE

2 months ago

Please let me know if is something you plan to support in the future. If not, I understand. It is required for our team, so I just want to know if I should start looking for alternative solutions.


2 months ago

Hello,

It's not something we could support ourselves, the rapid PRs are likely exceeding GitHub's webhook rate limit for a specific repo.

Best,
Brody


Status changed to Awaiting User Response railway[bot] 3 months ago


railway[bot]

2 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[bot] 2 months ago