Deployment Time Indicator #214

Closed
zoe wants to merge 1 commit from refs/pull/214/head into main
zoe commented 2026-04-29 10:05:06 +00:00 (Migrated from codeberg.org)

This Time is based on the builder logs, the timeouts specified. It is not possible to give an exact ETA but this approximate one will already help.
#189

This Time is based on the builder logs, the timeouts specified. It is not possible to give an exact ETA but this approximate one will already help. #189
anton commented 2026-04-29 18:48:40 +00:00 (Migrated from codeberg.org)

Unfortunately this will be wildly inaccurate if the application takes a long time to compile. Consider a large rust project that takes 20+ minutes to compile.

Unfortunately this will be wildly inaccurate if the application takes a long time to compile. Consider a large rust project that takes 20+ minutes to compile.
anton commented 2026-05-03 19:28:22 +00:00 (Migrated from codeberg.org)

Based on our conversation, we could indicate that the preparation takes x mins, and that the build time will vary depending on the size of the app. Something like this maybe (I put in random values right now, we'd need to establish a baseline):

remote: [x] Preparing deployment... (~ 1 mins)
remote: [x] Provisioning dedicated builder... (~ 5 mins)
remote: [x] Builder ready, downloading source... (...)
# not sure about all steps and their timing
Based on our conversation, we could indicate that the preparation takes x mins, and that the build time will vary depending on the size of the app. Something like this maybe (I put in random values right now, we'd need to establish a baseline): ``` remote: [x] Preparing deployment... (~ 1 mins) remote: [x] Provisioning dedicated builder... (~ 5 mins) remote: [x] Builder ready, downloading source... (...) # not sure about all steps and their timing ```
modalala commented 2026-05-04 00:03:17 +00:00 (Migrated from codeberg.org)

Maybe relevant for longer term decisions: see #211 "consider using time instead of chrono"
TLDR is that by eliminating chrono as a dependency we could reduce Caution's dependency tree significantly, but chrono handles time zones etc.

Maybe relevant for longer term decisions: see #211 "consider using time instead of chrono" TLDR is that by eliminating `chrono` as a dependency we could reduce Caution's dependency tree significantly, but `chrono` handles time zones etc.
anton commented 2026-05-25 03:15:27 +00:00 (Migrated from codeberg.org)

Closing this as it has conflicts and needs a better implementation. We also have https://codeberg.org/caution/platform/issues/250 which will drastically improve the speed of deployments.

Closing this as it has conflicts and needs a better implementation. We also have https://codeberg.org/caution/platform/issues/250 which will drastically improve the speed of deployments.

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
public/platform!214
No description provided.