Skip to content

Feature: Lack of messaging in Build history > Logs #908

Open
@uxarya-d

Description

Summary

Lack of messaging in Build history > Logs causes confusion for the user.

Motivation/Use case

  • User triggers build and navigates to the build history page to check logs.
  • It takes on an average ~3-5 mins for the logs to show up.
  • During this period; currently, we show a loader in the logs view.
  • Seeing a loader for a prolonged period (~3-5 mins) is confusing and the user might assume that the product (i.e. devtron) is broken/not functioning properly. The confusion gets magnified in the logs fullscreen view.

image
image

Proposal

Instead of just showing a loader, the product should be transparent and should convey the actual reason for the delay.

  1. To do this we can the worker status and worker message in the logs view until the logs show up.
    Proposed message format:
    Worker status: {{workerStatus}}
    Message: {{workerStatusMessage}}.
    Waiting for logs...

  2. This message should be cleared and replaced by logs once the logs are available.

AB#449

Metadata

Labels

ICA-AUG24Issue Cleanup Activity Aug 2024enhancementNew feature or requesttriage-acceptedIssue is accepted by the organisation to be worked on.wipIndicates that the work on issue has started.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions