10 months ago
Hi, I have had this issue before, but it was eventually solved by the dev team by changing something in the build order logic.
But now I am facing the issue again.
I have two services that are both sharing environment variables with eachother, but the project can only build if they finish building in the right order, and currently I don't have control over that.
The "Backend" service, needs to seed the database, and be fully online, before the "Storefront" service can start building fully (I am stalling it until backend is online) - this is because the storefront are generating some static pages, based on seed data.
As you can see in the screenshot, both the database and the backend is queued, so this project will never finish building.
I was wondering if there are any (new) ways to force a specific build order?
Project ID: c6866ee4-ec16-4585-839e-e00d6fc12ba1
Template ID: N6oq0e
4 Replies
10 months ago
As far as I know, build order cannot be controlled. If you need a service to explicitly deploy after another service, you can add a sleep to the start command
10 months ago
Or have some sort of github actions automation
10 months ago
But for a template, sleeping in the start command is likely your best bet
10 months ago
Hi 🙂
I think my deadlock starts before even get to any start commands being run unfortunately. Im only at the build stage for both services, where the wrong one is being prioritised