Deployment Time Indicator #214
No reviewers
Labels
No labels
Compat/Breaking
Component/Enclave-Builder
Component/Infrastructure
Deploy/BYOC
Deploy/Full-managed
Deploy/Self-hosted
Interface/API
Interface/CLI
Interface/Git
Interface/Web
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
public/platform!214
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/214/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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.
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):
Maybe relevant for longer term decisions: see #211 "consider using time instead of chrono"
TLDR is that by eliminating
chronoas a dependency we could reduce Caution's dependency tree significantly, butchronohandles time zones etc.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