Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Enhance Deployment Progress Bar #464

Open
wants to merge 13 commits into
base: staging
Choose a base branch
from

Conversation

TurkerKoc
Copy link
Member

@TurkerKoc TurkerKoc commented Mar 2, 2025

Enhanced Deployment Progress Visualization

This PR significantly improves the deployment progress tracking experience by redesigning how deployment steps are visualized and timed.

What Changed

  • Split Progress Tracking: Replaced the single combined progress bar with individual progress bars for each deployment step
  • Per-Step Timing: Added separate time estimations and completion tracking for each step in the deployment process
  • Improved Time Accuracy: Enhanced timing calculations with better transition tracking between deployment states
  • Visual Updates: Redesigned the progress UI with a vertical layout for better readability and understanding of the current deployment status
  • Detailed Remaining Time: Shows both per-step remaining time and total remaining time for the entire deployment

Why This Matters

These changes provide users with more detailed and granular information about their deployments. Instead of a single overall progress indicator, users can now see exactly which step is currently active and how much time remains for each individual step. This helps with:

  • Understanding which deployment phase is taking longer
  • Getting more accurate time estimations
  • Identifying exactly where a deployment might have failed
  • Better visibility into the overall deployment process

The vertical layout with individual progress bars delivers a more intuitive experience, making it easier to understand the current state of deployments at a glance.

Next Steps

  • Since we are not storing any additional information on failing steps of workflows. We can not show when the deployment is failed after refreshing the page.
  • To achieve this we need to store the status before the failure and timestamps of each step start/end times.

Screen Record

Screen.Recording.2025-03-10.at.18.22.31.mov

Copy link

codacy-production bot commented Mar 2, 2025

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
-0.12% (target: -1.00%) 0.00%
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (c97f532) 5225 631 12.08%
Head commit (0d2670a) 5278 (+53) 631 (+0) 11.96% (-0.12%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#464) 97 0 0.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more

Copy link

github-actions bot commented Mar 9, 2025

There hasn't been any activity on this pull request recently. Therefore, this pull request has been automatically marked as stale and will be closed if no further activity occurs within seven days. Thank you for your contributions.

@github-actions github-actions bot added the stale label Mar 9, 2025
@TurkerKoc TurkerKoc marked this pull request as ready for review March 10, 2025 17:27
@TurkerKoc TurkerKoc requested a review from a team as a code owner March 10, 2025 17:27
@github-actions github-actions bot removed the stale label Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant