GitLab CICD-pipeline crashes due to timeout even though it succeeded on Railway
I have a GitLab-project where I use CI/CD to automatically publish on Railway.
The strange thing is: Even though the builds succeed on Railway (https://railway.app/project/626fb4c9-9809-46bf-93fc-20ad46e06119/service/e726226c-2658-48d4-8d2e-5c8fbf4477dc?id=66552804-4b4a-4421-9c73-9594c0bd12ad), they fail due to timeout on GitLab (https://gitlab.com/Glitchy-Tozier/voteon.date/-/jobs/2985073689).
Any idea what to do about this?
Railway
Railway
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
12 Replies
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
What are you trying to tell me?
As far as I can tell I followed these instructions perfectly well.
@guess_wh0
replace
that
with
Hey, that seems to have worked! 🙂
Does this change anything about where build-step takes place?
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
Do you know why this isn't the default recommended command?
It seems like it's the current one breaks Gitlab CI/CD.
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
imo update blogpost to add -d
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
no problem!
Nice!
Thank you both for helping me
do you need help with anything else?
ah, np!