Clarification on Image Auto-Updates latency and programmatic redeploy via GraphQL API
gaboldev
PROOP

11 days ago

Hi Railway Team,

We are planning our production CI/CD strategy using immutable Docker images stored in GHCR and pushed to Railway via Image Auto-Updates. Before finalizing our setup, we'd like to clarify two points:

What is the maximum expected latency or polling interval for Railway to detect a tag update in an external registry and automatically trigger a deployment?

Is there a public GraphQL API mutation available that allows us to programmatically trigger an immediate redeploy (force-pulling the latest image tag) directly from our CI/CD pipeline to bypass polling wait times?

Thanks!

$20 Bounty

1 Replies

Railway
BOT

11 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 11 days ago


11 days ago

There is no fixed maximum delay for Image Update Detection

Yes, There is public API available to trigger new deployment, You can call the mutation environmentTriggersDeploy to trigger new deployment for the specific service

https://docs.railway.com/integrations/api/manage-deployments#deploy-a-specific-service-in-an-environment


Welcome!

Sign in to your Railway account to join the conversation.

Loading...