-
Notifications
You must be signed in to change notification settings - Fork 0
π§ HOTFIX: Railway Deployment Pipeline Corrections #29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -282,35 +282,46 @@ jobs: | |||||||||||||
| - name: π Deploy to Railway | ||||||||||||||
| id: deploy | ||||||||||||||
| run: | | ||||||||||||||
| curl -fsSL https://railway.app/install.sh | sh | ||||||||||||||
| echo "Installing Railway CLI..." | ||||||||||||||
| # Use direct binary download as fallback if install script fails | ||||||||||||||
| if ! curl -fsSL https://railway.app/install.sh | sh; then | ||||||||||||||
| echo "Standard install failed, trying alternative method..." | ||||||||||||||
| curl -L -o railway https://github.com/railwayapp/cli/releases/latest/download/railway-linux-amd64 | ||||||||||||||
| chmod +x railway | ||||||||||||||
| sudo mv railway /usr/local/bin/ | ||||||||||||||
| fi | ||||||||||||||
|
|
||||||||||||||
| echo "Logging into Railway..." | ||||||||||||||
| railway login --token ${{ secrets.RAILWAY_TOKEN }} | ||||||||||||||
| railway up --service neurobank-fastapi | ||||||||||||||
|
|
||||||||||||||
| echo "Deploying to Railway..." | ||||||||||||||
| railway up --service neurobank-fastapi --detach | ||||||||||||||
|
|
||||||||||||||
| echo "Deployment initiated successfully!" | ||||||||||||||
| env: | ||||||||||||||
| RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }} | ||||||||||||||
|
|
||||||||||||||
| - name: π₯ Post-Deployment Health Check | ||||||||||||||
| run: | | ||||||||||||||
| echo "Waiting for deployment to stabilize..." | ||||||||||||||
| sleep 30 | ||||||||||||||
| sleep 60 | ||||||||||||||
|
||||||||||||||
| sleep 60 | |
| sleep $DEPLOYMENT_WAIT_TIME |
Copilot
AI
Jul 21, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The error handling with '|| echo "Status check completed"' masks potential failures. The status check failure should be logged more clearly to help with debugging deployment issues.
| railway status --service neurobank-fastapi || echo "Status check completed" | |
| if ! railway status --service neurobank-fastapi; then | |
| echo "β Deployment status check failed!" | |
| echo "Please check the Railway dashboard for more details and ensure the service is running correctly." | |
| exit 1 | |
| fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The hardcoded architecture 'linux-amd64' may not work on all GitHub Actions runners. Consider detecting the architecture dynamically or using a more generic approach that works across different runner types.