If a builder gets stuck, we have no way to know why it failed or how to fix it. We have no logs, no metrics, or anything.
If a builder gets stuck, we have no way to know why it failed or how to fix it. We have no logs, no metrics, or anything.
If a builder gets stuck, we have no way to know why it failed or how to fix it. We have no logs, no metrics, or anything.
Some thoughts on how this could work:
Related to #132
Backlog duplicate audit: #78 (store build logs in S3 and expose them via CLI/UI) is a narrower subset of this builder observability issue. Keeping this as the primary ticket for builder log/metric visibility; #78 is being closed in favor of this issue.
No due date set.
No dependencies set.
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?