Deploys are stuck in waiting for CI
andreisurzhan
HOBBYOP

2 months ago

Steps to reproduce

1. Have 2 contributors in the github repo
2. Have 2 environments: development and production
3. Auto Deploy deploy development from development branch
4. Auto Deploy production from main branch

  1. Add github actions to your project

  2. Mark both deploy settings in both environments in railway to wait for ci

  3. Submit change to development branch from github account that is not in railway project

  4. Approve deployment in development in railway using your railway account

  5. Create PR in github from development to main

  6. Wait till github actions are done

  7. Check deployment status in railway for development environment

Actual result: development deployment is stuck with waiting for CI for commit/s in development branch even through github actions passed

Expected result: deployment should happen after github actions pass

$10 Bounty

6 Replies

Railway
BOT

2 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!


ilyassbreth
FREE

2 months ago

railway's "wait for ci" checks ALL github check suites, not just your actions. even if actions pass, other apps can block it

check your commit on github for ALL checks - look for failing ones from old railway projects, github pages, codecov, or other installed apps. remove unused apps from github settings → applications

quick fix is to disable "wait for ci" temporarily in railway service settings if urgent

hope this help you slightly_smiling_face emoji


ilyassbreth

railway's "wait for ci" checks ALL github check suites, not just your actions. even if actions pass, other apps can block itcheck your commit on github for ALL checks - look for failing ones from old railway projects, github pages, codecov, or other installed apps. remove unused apps from github settings → applicationsquick fix is to disable "wait for ci" temporarily in railway service settings if urgenthope this help you

andreisurzhan
HOBBYOP

2 months ago

Thank you so much for your reply.

I looked into GH apps and actions.

I had only Railway and Cursor.

But what I noticed that I had extra environments in GH. They had references to the same projects in Railway. Could it be that when I renamed my projects in railway - it duplicated Environments in GH?


andreisurzhan

Thank you so much for your reply. I looked into GH apps and actions.I had only Railway and Cursor.But what I noticed that I had extra environments in GH. They had references to the same projects in Railway. Could it be that when I renamed my projects in railway - it duplicated Environments in GH?

ilyassbreth
FREE

2 months ago

yes railway doesn't always clean up github artifacts when you rename projects - this is a known issue. check your repo's checks tab on recent commits to see if there are failing railway checks from old project names. cleaning up old environments might help, but the main thing is making sure no old railway check suites are failing. you can also try disconnecting/reconnecting the repo in railway settings to refresh everything


andreisurzhan
HOBBYOP

2 months ago

still happening, I will give a shot disconnecting and connecting back.

i will post later. Thank you

P.S. I won't disappear and will update. And make sure solution is posted.


andreisurzhan
HOBBYOP

2 months ago

Closing the loop here.

It seems everything is working fine.
Indeed i needed to wait for all of the processes to finish and then waiting for CI resolves.

Removing stale projects from github after renaming projects in railway seemed to resolve it.

Cheers folks. and Thanks you Ilyassbreth for helping.


Loading...