Railway CLI deploy now logs everything? How do stop this behavour.
My ci/cd on github uses railway cli to deploy my changes. Yesterday, using this command would start the build process for all them at once
but now it deploys one at a time, waiting for each to finish before starting the next.
how do i prevent this behavior?
16 Replies
Project ID:
N/A
are these commands being ran in a matrix? from my prospective theres no reason why these commands shouldn't run one after the other
they're ran on a single runner
but I guess i'm just confused why the behavior changed?
I don't want to run up my github build time bill, and having all the logs come through before it finished 100x the build time on github
perhaps you want to use --ci
do you have a docs link for the flags?
what does ci do?
😦 5x time
Solution
i see, but why did it randomly change the behavour? or was it supposed to be like all along, and was bugged?
or was it supposed to be like all along, and was bugged?correct the cli is supposed to wait for the deploy to fail / succeed so that it can fail the action if the deploy failed
you have the flags backwards lol
but docs say
oh
fixed, thanks as always brody!
so they arent actually running in parallel, they just arent running for long enough for you to noticed that they arent running in parallel
correct, it would just kick off the builds in a synchronous fashion